'java -version' on a just compiled JDK seems sufficient to reproduce:


<mock-chroot> sh-5.0# ./build/jdk8.build/images/j2sdk-image/bin/java -version
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f178f9a3976, pid=21, tid=0x00007f1771386700
#
# JRE version: OpenJDK Runtime Environment (8.0_242-b06) (build 1.8.0_242-ea-b06)
# Java VM: OpenJDK 64-Bit Server VM (25.242-b06 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x8d7976][thread 139738657339136 also had an error]
openjdk version "1.8.0_242-ea"
OpenJDK Runtime Environment (build 1.8.0_242-ea-b06)
OpenJDK 64-Bit Server VM (build 25.242-b06, mixed mode)
  Node::Node(unsigned int)+0x26
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.242.b06-0.0.ea.fc32.x86_64/openjdk/hs_err_pid21.log

[error occurred during error reporting , id 0xb]

#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Aborted (core dumped)

Created attachment 1655704 [details]
hs_err file

Similar issues on java-11-openjdk: https://koji.fedoraproject.org/koji/taskinfo?taskID=41003490

Not sure why you have a patch confusingly named with the bug ID of a Shenandoah S390 fix, but the relevant fix is https://bugs.openjdk.java.net/browse/JDK-8224851 which I already have backported to 11u.

(In reply to Andrew John Hughes from comment #3)
> Similar issues on java-11-openjdk:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=41003490

Not quite the same. See my PR for getting it moving again (except the s390x issue which I don't know what's causing it yet):
https://src.fedoraproject.org/rpms/java-11-openjdk/pull-request/65

> Not sure why you have a patch confusingly named with the bug ID of a
> Shenandoah S390 fix, but the relevant fix is
> https://bugs.openjdk.java.net/browse/JDK-8224851 which I already have
> backported to 11u.

Just an oversight. Thanks for noticing it. Are you planning on proposing the backport for 11.0.7 upstream?

(In reply to Severin Gehwolf from comment #4)
> (In reply to Andrew John Hughes from comment #3)
> > Similar issues on java-11-openjdk:
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=41003490
> 
> Not quite the same. See my PR for getting it moving again (except the s390x
> issue which I don't know what's causing it yet):
> https://src.fedoraproject.org/rpms/java-11-openjdk/pull-request/65
> 

Yeah, I was thinking of the aarch64 issue being the same. I didn't get to trying java-1.8.0-openjdk with that patched just yet, and didn't realise you were looking at this too. I couldn't make head nor tail of the java-11-openjdk failure once the aarch64 fix was patched (the build logs for it are awful), so good to hear that -fcommon helps it makes progress.

Incidentally, if you're going to include the +10 changes from f31 in this PR, can you please restore my changelog entry to go with it? Or, alternatively, I can add your change to the version I have waiting.

> > Not sure why you have a patch confusingly named with the bug ID of a
> > Shenandoah S390 fix, but the relevant fix is
> > https://bugs.openjdk.java.net/browse/JDK-8224851 which I already have
> > backported to 11u.
> 
> Just an oversight. Thanks for noticing it. Are you planning on proposing the
> backport for 11.0.7 upstream?

No problem. I just thought it's odd when I copied the bug ID to lookup your bug and ended up at my s390 fix :) Thankfully, the correct one was in the comment above.

And yes, sorry, I should have been clearer. I mentioned it so we wouldn't both end up proposing it. I'll do that today. I already have it locally, I just need to do the whole webrev and e-mail dance with it.

*** Bug 1799529 has been marked as a duplicate of this bug. ***

This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

A fastdebug build asserts with -Xint:

<mock-chroot> sh-5.0# ./build/jdk8.build/images/j2sdk-image/bin/java -Xint -version
openjdk version "1.8.0_242-ea-fastdebug"
OpenJDK Runtime Environment (build 1.8.0_242-ea-fastdebug-b06)
OpenJDK 64-Bit Server VM (build 25.242-b06-fastdebug, interpreted mode)
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=/genOopClosures.hpp:202
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.242.b06-0.0.ea.fc32.x86_64/openjdk/hotspot/src/share/vm/memory/genOopClosures.hpp:202), pid=59, tid=0x00007fd84f8f8700
#  guarantee(obj->is_oop_or_null()) failed: invalid oop: 0x0000000000000000
#
# JRE version: OpenJDK Runtime Environment (8.0_242-b06) (build 1.8.0_242-ea-fastdebug-b06)
# Java VM: OpenJDK 64-Bit Server VM (25.242-b06-fastdebug interpreted mode linux-amd64 compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.242.b06-0.0.ea.fc32.x86_64/openjdk/hs_err_pid59.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Current thread is 140567024469760
Dumping core ...
Aborted (core dumped)

The same with -Xcomp (or no flag):
<mock-chroot> sh-5.0# ./build/jdk8.build/images/j2sdk-image/bin/java -Xcomp -version
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=/node.cpp:301
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.242.b06-0.0.ea.fc32.x86_64/openjdk/hotspot/src/share/vm/opto/node.cpp:301), pid=75, tid=0x00007f4ae3859700
#  assert(Compile::current() == C) failed: must use operator new(Compile*)
#
# JRE version: OpenJDK Runtime Environment (8.0_242-b06) (build 1.8.0_242-ea-fastdebug-b06)
# Java VM: OpenJDK 64-Bit Server VM (25.242-b06-fastdebug compiled mode linux-amd64 compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /builddir/build/BUILD/java-1.8.0-openjdk-1.8.0.242.b06-0.0.ea.fc32.x86_64/openjdk/hs_err_pid75.log
[thread 139959618332416 also had an error]

[error occurred during error reporting , id 0xb]

#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Current thread is 139959621490432
Dumping core ...
Aborted (core dumped)

Some progress here. It seems another case of some UB in hotspot. The best I could come up
with so far is a list of flags which makes the build pass:

-fno-tree-pta -fno-tree-scev-cprop -fno-tree-sink -fno-tree-slp-vectorize -fno-tree-slsr -fno-tree-sra
-fno-tree-switch-conversion -fno-tree-tail-merge -fno-tree-ter -fno-tree-vrp -fno-unit-at-a-time
-fno-unswitch-loops -fno-vect-cost-model -fno-version-loops-for-strides -fno-tree-coalesce-vars
-fno-tree-copy-prop -fno-tree-dce -fno-tree-dominator-opts -fno-tree-dse -fno-tree-forwprop -fno-tree-fre
-fno-tree-loop-distribute-patterns -fno-tree-loop-distribution -fno-tree-loop-vectorize
-fno-tree-partial-pre -fno-tree-phiprop -fno-tree-pre

It's a long list which could likely get narrowed down further. Anyway, this will help me narrow down
where things go wrong and hopefully find the OpenJDK patches to backport so that we can build without
those flags.

https://src.fedoraproject.org/fork/jerboaa/rpms/java-1.8.0-openjdk/commits/gcc10_changes

This tree --^ has the changes. A scratch build with that is currently running (it passed on
3 architectures at least):
https://koji.fedoraproject.org/koji/taskinfo?taskID=41481433

I've opened a PR with the GCC flags added as work-around.
This is so that we are unblocked for the upcoming release:
https://src.fedoraproject.org/rpms/java-1.8.0-openjdk/pull-request/99

Build with the workaround flags is now in F32: https://koji.fedoraproject.org/koji/buildinfo?buildID=1477017

As soon as a backport of JDK-8233880 is in OpenJDK 8u proper, we can get rid of this ugly work-around.

This will be released in 8u262 with:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-e418151dc3