JDK-8038297 : Avoid placing CTI immediately following cbcond instruction on T4
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs22
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: sparc
  • Submitted: 2014-03-25
  • Updated: 2019-09-13
  • Resolved: 2014-04-11
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.
8u20Fixed 9 b11Fixed
Related Reports
Cloners :  
Relates :  
Code generated for T4 and related SPARC processors should avoid placing Control Transfer Instructions [CTI] such as call and retl immediately following a cbcond instruction.

I asked Igor to look on this. He recently worked on an other cbcond problem: 8035283.

Looks like it is reasonable request. Richard, can you attach your microbenchmark to the bug report so we can measure the same performance difference?

Is it the problem only on T4? Or also on all newer T-SPARC?

Richard, can you point any documents about this? There was only restriction on placing an other cbcond instruction after first.