JDK-8304587 : Issue with C calling conventions in 11u ad file on windows
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 11.0.19,16
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: windows
  • CPU: x86
  • Submitted: 2023-03-21
  • Updated: 2023-03-21
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.
Other
tbdUnresolved
Related Reports
Relates :  
Relates :  
Relates :  
Description
In JDK-8304389 we fixed a regression in 11u with basically undoing a previous change (JDK-8248238) that just made the issue appear. We needed a quick-fix before delivering 11.0.19. See JDK-8304389 for details.

It seems the issue is fixed differently in recent JDKs (16+), at least it can not be reproduced there. But potentially C2 just generates different code in 16+ so that the issue can not be reproduced with the same test. Unfortunately the test is an SAP internal one.

Find the root cause and fix it.  

As it is not clear whether the root cause is fixed in 16+ I do not assign this to 11u only.
Comments
One issue seems to be that RSI is used as _byte_map_base for some GCs. Another one is fixed in later JDK versions: JDK-8254252
21-03-2023

ILW = C calling convention issue on Windows that is hidden without JDK-8248238, no crash without JDK-8248238, no workaround = MLH = P4
21-03-2023