ARM32 crash since 8283326: Implement SafeFetch statically

[Thomas Stüfe]

Yes, please open a bug report, and if possible attach a hs-err file or at
least the crash stack. The patch was tested on arm32, so I'm not sure yet
what's wrong.

Note that I do a cross build for arm32, I don't build natively.

Cheers, Thomas

On Tue, Apr 19, 2022 at 11:52 AM Marc Hoffmann <hoffmann at mountainminds.com>
wrote:

> Dear Hotspot developers,
>
> Marc here from the JaCoCo project. Since the following commit the native
> arm32 build seems to be broken:
>
> 8283326: Implement SafeFetch statically
> Reviewed-by: dholmes, mdoerr, akozlov, lucy
>
>
> https://github.com/openjdk/jdk/commit/bdf8a2a2050393e91800786f8d5a5d6805f936eb
> <
> https://github.com/openjdk/jdk/commit/bdf8a2a2050393e91800786f8d5a5d6805f936eb
> >
>
>
> The build crashes reproducible with the following error:
>
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0xb43939e0, pid=16897, tid=16902
> #
> # JRE version: OpenJDK Runtime Environment (19.0) (build
> 19-internal-adhoc..workspace)
> # Java VM: OpenJDK Server VM (19-internal-adhoc..workspace, mixed mode, g1
> gc, linux-arm)
> # Problematic frame:
> # v  ~StubRoutines::atomic_add
> #
> # Core dump will be written. Default location: /workspace/make/core
> #
> # If you would like to submit a bug report, please visit:
> #   https://bugreport.java.com/bugreport/crash.jsp
> #
> See crash report file attached.
>
> Should I open a bug report for this or is this already known?
>
> Thanks for looking into this and best regards,
> -marc
>
>
>
>