On Sun, 10 Oct 2021 13:05:40 GMT, Jie Fu 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 tar
On Mon, 11 Oct 2021 00:47:38 GMT, David Holmes wrote:
> Hi Jie,
>
> Can we not just disable the warning in this specific test?
>
> Thanks, David
Thanks @dholmes-ora for your review.
According to this comment [1], gtest source code warnings are disabled in build
script.
Maybe, it would be bet
On 9/10/2021 3:58 pm, Aleksey Shipilev wrote:
Hi,
This does not look a build issue per se, but rather a Hotspot bug.
The SIGILL in ThreadGroup.add looks to me like an issue with atomic
operations as that is the first synchronized method that gets executed
during VM initialization.
David
--
On Sun, 10 Oct 2021 13:05:40 GMT, Jie Fu 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 tar
This fix changes the AbsPathsInImage test to skip *.dSYM directories.
-
Commit messages:
- Update AbsPathsInImage.java
Changes: https://git.openjdk.java.net/jdk/pull/5885/files
Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=5885&range=00
Issue: https://bugs.openjdk.java.ne
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:
