In JDK-8319818 the stringop-overflow warnings were disabled for linux-aarch64 (fastdebug). With the changes in JDK-8319883 additional stringop-overflow warnings are produced with GCC 13.2.0, this time for linux-x64-zero (fastdebug). The warnings are related to GCC thinking JavaThread:current (and Thread::current) may return nullptr where in fact they can't. I tried several ways to convince GCC about this fact but in the end failed.
This change disables the warning for the affected files (only). I'm not in love with that solution but I've run out of ideas at this point. An alternative would be to disable the warning globally, which has its own set of pros and cons. ------------- Commit messages: - 8320212: Disable GCC stringop-overflow warning for affected files Changes: https://git.openjdk.org/jdk/pull/16702/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=16702&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8320212 Stats: 11 lines in 1 file changed: 4 ins; 7 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/16702.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/16702/head:pull/16702 PR: https://git.openjdk.org/jdk/pull/16702
