JDK-8256237 : Zero: non-PCH build fails after JDK-8253064
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-11-11
  • Updated: 2020-11-19
  • Resolved: 2020-11-11
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 16
16 b25Fixed
Related Reports
Duplicate :  
Relates :  
Description
This shows up in GH actions, and reproduces locally:

/home/shade/trunks/jdk/src/hotspot/share/runtime/monitorDeflationThread.cpp: In static member function 'static void MonitorDeflationThread::initialize()':
/home/shade/trunks/jdk/src/hotspot/share/runtime/monitorDeflationThread.cpp:42:32: error: 'Universe' has not been declared
   42 |   Handle thread_group (THREAD, Universe::system_thread_group());
      |                                ^~~~~~~~


Comments
Yeah, Zero and Minimal build configs are good at finding "missing" includes that are transitively available through many other VM options otherwise.
11-11-2020

Changeset: 59965c17 Author: Aleksey Shipilev <shade@openjdk.org> Date: 2020-11-11 19:52:18 +0000 URL: https://github.com/openjdk/jdk/commit/59965c17
11-11-2020

Hmmm... This didn't show up in any of my Mach5 Tier1-8 testing. Update: I just double checked my Ubuntu 16.04 machine and I do non-PCH builds there also. However, I've never built Zero and I don't know if Mach5 builds Zero.
11-11-2020