JDK-7085137 : -XX:+VerifyOops is broken
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs22
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-08-30
- Updated: 2011-10-07
- Resolved: 2011-09-30
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.
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 7 | JDK 8 | Other |
|---|---|---|
7u2Fixed  |
8Fixed |
hs22Fixed |
Related Reports
|
Relates :
|
Description
I hit my new assert about different code emit size (7063629) when I specified -XX:+VerifyOops on sparc. It uses set((intptr_t)msg, O0) instruction to set address of message which is new each time, as result set() size could be different. Replace set() it with patchable_set() to be always 8 instructions.
Comments
|