RFR: 8326936: RISC-V: Shenandoah GC crashes due to incorrect atomic memory operations

[MaxXing]

On Fri, 1 Mar 2024 13:36:01 GMT, Fei Yang <fyang at openjdk.org> wrote:

>> Hi, I don't witness such an issue when running those regression tests with jdk binaries built with native GCC-12 on Licheepi-4a or Unmatched boards. Do you know why? Does that mean this will only trigger for jdk binaries built with GCC-13? Guess @robehn who owns https://bugs.openjdk.org/browse/JDK-8316186 might also be interested in this.
>
>> @RealFYang Thanks for your comments!
>> 
>> > BTW: I am curious about why GCC old versions like GCC-11/12 would work. Can you take a look? Thanks.
>> 
>> I'm trying to figure this out. Are you building in `release` mode? `fastdebug` enables `CHECK_UNHANDLED_OOPS` macro, which adds explicit null checks before every oop dereferences, so the bug will not appear.
> 
> Yeah, I am talking about linux-riscv64 release build built with GCC-11/12.

@RealFYang @robehn Thanks for your review!

-------------

PR Comment: https://git.openjdk.org/jdk/pull/18039#issuecomment-1978290359