-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 11, 12
-
Component/s: hotspot
-
b13
-
x86
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8213065 | 11.0.2 | Vladimir Kozlov | P3 | Resolved | Fixed | b02 |
Recently there have been couple of high priority issues with regards to avx512 high bank of XMM register (XMM16-XMM31) usage by C2: JDK-8207746, JDK-8209735
Please find below a patch which attempts to clean up the XMM register handling by using register groups:
http://cr.openjdk.java.net/~vdeshpande/xmm_reg/webrev.01/
The patch provides a restricted set of registers to the match rules in the ad file based on the underlying architecture.
The aim is to remove special handling/workaround from macro assembler and assembler.
By removing the special handling, the patch reduces the overall code size by about 1800 lines of code.
Best Regards,
Sandhya
Please find below a patch which attempts to clean up the XMM register handling by using register groups:
http://cr.openjdk.java.net/~vdeshpande/xmm_reg/webrev.01/
The patch provides a restricted set of registers to the match rules in the ad file based on the underlying architecture.
The aim is to remove special handling/workaround from macro assembler and assembler.
By removing the special handling, the patch reduces the overall code size by about 1800 lines of code.
Best Regards,
Sandhya
- backported by
-
JDK-8213065 Update avx512 implementation
-
- Resolved
-
- relates to
-
JDK-8211272 x86_32 build failures after JDK-8210764 (Update avx512 implementation)
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-