Bug ID: JDK-8144448 Avoid placing CTI immediately following or preceding RDPC instruction

Type: Bug
Component: hotspot
Sub-Component: compiler
Affected Version: 8u25,9,10

Priority: P3
Status: Resolved
Resolution: Fixed
OS: generic
CPU: sparc

Submitted: 2015-12-01
Updated: 2019-09-13
Resolved: 2017-06-29

Versions (Unresolved/Resolved/Fixed)

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.

JDK 10
10 b21Fixed

Code generated for new SPARC processors should avoid placing Control Transfer Instructions [CTI] such as call, return and branches immediately following or preceding a RDPC instruction.

ILW = Performance problem with C2, SPARC only, no workaround = MMH = P3
20-02-2017
9-defer-SQE-ok: agreed on defer request reason
17-06-2016
9-defer-request: Instructions emitted by the C2 compiler do not adhere to the guidelines introduced by the newest SPARC processors. As a result, the performance of generated code is "suboptimal" in those new platforms. (There is no performance regression, though, as that was always the case, i.e., C2 did not degrade over time.) The goal of this bug is to address this issue, but that can be done once all correctness issues (bugs) have been addressed.
15-06-2016
[~sanzinger], something you might consider as well.
01-12-2015

Relates :	JDK-8200288 - Compilation fails with "assert(!(is_cti(prev) && is_cti(insn))) failed: CTI-CTI not allowed" on SPARC
Relates :	JDK-8038297 - Avoid placing CTI immediately following cbcond instruction on T4