Hi, please consider. I have been witnessing this build issue with GCC 14 for quite some time on linux-riscv64. Seems that GCC 14's deeper inlining optimizations interact badly with stringop-overflow here. And I always need to pass `--disable-warnings-as-errors` to work around it. Similar to [JDK-8382395](https://bugs.openjdk.org/browse/JDK-8382395), this disables this warning for the affected file as well.
configure command: sh configure --with-debug-level=fastdebug --with-jvm-variants=server --enable-unlimited-crypto --with-native-debug-symbols=internal --with-boot-jdk=/home/openeuler/tools/boot-jdk --with-jtreg=/home/openeuler/tools/jtreg --with-gtest=/home/openeuler/tools/googletest --------- - [x] I confirm that I make this contribution in accordance with the [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). ------------- Commit messages: - 8382522: Disable stringop-overflow in safepointMechanism.cpp Changes: https://git.openjdk.org/jdk/pull/30823/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=30823&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8382522 Stats: 1 line in 1 file changed: 1 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/30823.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/30823/head:pull/30823 PR: https://git.openjdk.org/jdk/pull/30823
