JDK-8262912 : ciReplay: replay does not simulate unresolved classes
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 17,18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-03-03
  • Updated: 2021-11-10
  • Resolved: 2021-10-15
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 18
18 b20Fixed
Related Reports
Blocks :  
Blocks :  
Relates :  
Description
If a class was unresolved in the replay file, but resolved at replay time, replay simply outputs the warning:
"Warning: entry was unresolved in the replay data"

Instead, it should simulate the class still being unresolved.
Comments
Changeset: 4cb7124c Author: Christian Hagedorn <chagedorn@openjdk.org> Date: 2021-10-15 07:38:38 +0000 URL: https://git.openjdk.java.net/jdk/commit/4cb7124c1e9c5fd1d3a82fd8933cc63fefde9531
15-10-2021

This may be hard to reproduce currently, since replay happens before most classes are loaded, but it should be needed in order to implement JDK-8254110.
09-08-2021