-
Bug
-
Resolution: Fixed
-
P4
-
openjdk8u422
-
b02
-
generic
-
linux, os_x, solaris, aix
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8360901 | shenandoah8u432 | Andrew Hughes | P4 | Resolved | Fixed | b02 |
8u still use the legacy HotSpot build system which is not fully integrated with the autoconf system. Variables defined by configure thus have to be explicitly passed down to the separate HotSpot build.
ADLC is a tool used at build-time and so the flags it uses don't impact on the end product. So, for a long time, it has been ignoring these flags defined by configure and using just its own minimal set.
However, with newer compilers, this means that the code is compiled to a newer version of the C++ standard, as the default has changed in GCC 6 and later (see
We should fix the ADLC build to use the same flags as the rest of the build. The impact should be negligible, given the same flags are already used in the code that is actually shipped.
This does not affect 9+ where HotSpot's build system has been replaced with full integration in the autoconf system.
- backported by
-
JDK-8360901 Flags introduced by configure script are not passed to ADLC build
-
- Resolved
-
- duplicates
-
JDK-8281097 Flags Introduced by configure script Are Not Passed to ADLC build
-
- Closed
-
-
JDK-8281098 Flags Introduced by configure script Are Not Passed to ADLC build
-
- Closed
-
- is cloned by
-
JDK-8325213 Flags introduced by configure script are not passed to ADLC build
-
- Resolved
-
- relates to
-
JDK-8151841 Build needs additional flags to compile with GCC 6
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk8u-dev/4106121e
-
Review(master) openjdk/jdk8u-dev/357