-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 17, 21
-
b05
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8335958 | 17.0.13 | George Adams | P4 | Resolved | Fixed | b01 |
JDK-8341249 | 11.0.26 | Severin Gehwolf | P4 | Resolved | Fixed | b01 |
The general approach to dealing with this is to ensure the HotSpot macro is not defined when including potentially problematic 3rd party headers, and reinstate the HotSpot macro after those includes.
It would be helpful to have a utility for performing this dance, rather than recreating it multiple times.
We should also arrange for -DNDEBUG to be defined in release builds to suppress the expansion of the standard assert macro.
- backported by
-
JDK-8335958 Support dealing with standard assert macro
- Resolved
-
JDK-8341249 Support dealing with standard assert macro
- Resolved
- duplicates
-
JDK-8299380 conflict assert definitions
- Closed
- relates to
-
JDK-8321558 HotSpot Style Guide needs update regarding stdlib assert
- Open
-
JDK-8007770 fix name clash of assert macro in debug.hpp with libc's assert macro
- Closed
-
JDK-8318078 ADLC: pass ASSERT and PRODUCT flags
- Resolved
-
JDK-8299380 conflict assert definitions
- Closed
- links to
-
Commit openjdk/jdk17u-dev/89dd23f2
-
Commit openjdk/jdk/3e2314d0
-
Commit(master) openjdk/jdk11u-dev/06d87ca6
-
Review openjdk/jdk17u-dev/1940
-
Review openjdk/jdk/11770
-
Review(master) openjdk/jdk11u-dev/2937
-
Review(master) openjdk/jdk17u-dev/2689