On Tue, 21 Apr 2026 02:22:39 GMT, Dingli Zhang <[email protected]> wrote:
>> 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). > > Dingli Zhang has updated the pull request with a new target base due to a > merge or a rebase. The pull request now contains two commits: > > - Merge branch 'master' into JDK-8382522 > - 8382522: Disable stringop-overflow in safepointMechanism.cpp LGTM. This is also happening when building fastdebug with GCC 13.3.0 on Ubuntu 24.04.1 RISC-V. And there seems to be quite a few related GCC bugs still pending there. Like: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107694 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475 ------------- Marked as reviewed by fyang (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/30823#pullrequestreview-4151538192
