JDK-6953539 : after 6892658 c1 reports that it doesn't inline StringBuffer.append
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: solaris_9
- CPU: sparc
- Submitted: 2010-05-18
- Updated: 2010-09-24
- Resolved: 2010-06-01
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 6 | JDK 7 | Other |
|---|---|---|
| 6u21pFixed | 7Fixed  |
hs19Fixed |
Related Reports
|
Relates :
|
Description
6892658 added intrinsic ids for several StringBuffer/StringBuilder methods which triggered some long dormant logic in try_inline_intrinsic which acts as if it bails out of inlining if an intrinsic is synchronized. It should simply return false to indicate that it didn't do anything and not set the inline bailout message.
Comments
|