On Sun, 10 Oct 2021 13:05:40 GMT, Jie Fu <ji...@openjdk.org> wrote: > Hi all, > > gtest build fails due to stringop-overflow warning with gcc11. > > This is because gcc11 seems to be smart enough to detect the following > stringop-overflow at test/hotspot/gtest/memory/test_guardedMemory.cpp:125:11. > > * For target hotspot_variant-server_libjvm_gtest_objs_test_guardedMemory.o: > In file included from /usr/include/string.h:495, > from > /home/jdk/src/hotspot/share/utilities/globalDefinitions_gcc.hpp:35, > from > /home/jdk/src/hotspot/share/utilities/globalDefinitions.hpp:35, > from /home/jdk/src/hotspot/share/memory/allocation.hpp:29, > from > /home/jdk/test/hotspot/gtest/memory/test_guardedMemory.cpp:25: > In function 'void* memset(void*, int, size_t)', > inlined from 'virtual void > GuardedMemory_buffer_overrun_tail_Test::TestBody()' at > /home/jdk/test/hotspot/gtest/memory/test_guardedMemory.cpp:125:11:
Hi Jie, Can we not just disable the warning in this specific test? Thanks, David ------------- PR: https://git.openjdk.java.net/jdk/pull/5881
