On Mon, 20 Apr 2026 10:07:41 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). I don't see why an issue on one platform should force this change on all platforms. And what exactly is being complained about? Is there a code issue? Is there a gcc14 bug? Please explain further. Thanks ------------- PR Comment: https://git.openjdk.org/jdk/pull/30823#issuecomment-4280415984
