JDK-7048030 : is_scavengable changes causing compiler to embed more constants
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs21
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic,solaris_10
- CPU: generic,x86
- Submitted: 2011-05-24
- Updated: 2011-08-02
- Resolved: 2011-06-09
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 |
|---|---|---|
7Fixed  |
8Fixed |
hs21Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The fix for 7041789 corrected the meaning of is_scavengable to really mean what it says. Unfortunately there were some places that were really using the change as a proxy for !is_perm. in particular in ciObject::can_be_constant and should_be_constant we will now embed constants that we didn't used as long as they are in tenured. The code should be changed from !is_scavengable to is_perm.
Comments
|