JDK-8238896 : Massive x86_32 crashes after JDK-7175279 (Don't use x87 FPU on x86-64)
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 15
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2020-02-11
  • Updated: 2020-07-17
  • Resolved: 2020-02-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 15
15 b11Fixed
Related Reports
Duplicate :  
Relates :  
Description
In current jdk/jdk, lots of tests fail with x86_32 builds.

$ CONF=linux-x86-server-fastdebug make images run-test TEST=tier1

$ grep assert build/linux-x86-server-fastdebug/test-support/jtreg_test_hotspot_jtreg_tier1/jtreg.log | sort | uniq -c
      3 #  assert(is_single_cpu() && !is_virtual()) failed: type check
     72 #  assert(src->fpu() == 0) failed: input must be on TOS
     23 #  assert(src->fpu() == dest->fpu()) failed: currently should be nothing to do

Comments
[~shade], could you please confirm that the defect is fixed in jdk15 w/ the patch? if it's so, please close/verify this bug as 'verified'
15-07-2020

URL: https://hg.openjdk.java.net/jdk/jdk/rev/c22087442921 User: shade Date: 2020-02-13 16:06:27 +0000
13-02-2020

RFR: https://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2020-February/037001.html
12-02-2020

Candidate fix in testing: https://cr.openjdk.java.net/~shade/8238896/webrev.01/ Two issues: the (obviously) missing "break" and the (non-obviously) semantics-breaking move that runs afoul of is_single_fpu and is_single_xmm inclusiveness (see the warning comment here: http://hg.openjdk.java.net/jdk/jdk/file/7ef41e83066b/src/hotspot/share/c1/c1_LIR.hpp#l371)
12-02-2020

Looking into this, added [~vlivanov] to the watch list meanwhile.
11-02-2020