In JDK-8320212 I disabled the stringop-overflow warning for four files:
* handshake.cpp
* jvmciCodeInstaller.cpp
* jvmtiTagMap.cpp
* synchronizer.cpp
This was needed to address build failures with linux/zero (fastdebug). The underlying reason appears to be that GCC 13.2.0 incorrectly believes that JavaThread:current (really: Thread::current) can return nullptr, where in fact it can't. The assert in Thread::current, which calls the ATTRIBUTE_NORETURN report function on failure, should be sufficient to give GCC the necessary information, but apparently that doesn't always work.
Disabling the warning was a last resort to fix the immediate build issue. It would be preferable to find another, better way to address the warning/failing builds.
* handshake.cpp
* jvmciCodeInstaller.cpp
* jvmtiTagMap.cpp
* synchronizer.cpp
This was needed to address build failures with linux/zero (fastdebug). The underlying reason appears to be that GCC 13.2.0 incorrectly believes that JavaThread:current (really: Thread::current) can return nullptr, where in fact it can't. The assert in Thread::current, which calls the ATTRIBUTE_NORETURN report function on failure, should be sufficient to give GCC the necessary information, but apparently that doesn't always work.
Disabling the warning was a last resort to fix the immediate build issue. It would be preferable to find another, better way to address the warning/failing builds.
- relates to
-
JDK-8320212 Disable GCC stringop-overflow warning for affected files
-
- Resolved
-
- links to
-
Review(master)
openjdk/jdk/26067