JDK-8085832 : Optimize main and post loop out when pre loop is found empty
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-06-04
  • Updated: 2024-03-08
  • Resolved: 2015-06-10
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 9
9 b70Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Description
In JDK-8078866, the pre loop is optimized out but the main/post loops are not. If the pre loop’s limit is still an opaque node, then the compiler has not been able to optimize the pre loop based on its limited number of iterations yet. I don’t see what optimization would remove stuff from the pre loop that wouldn’t have removed the same stuff from the initial loop, had it not been cloned. So it should be safe to remove the main and post loops.
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/421989a11af8 User: lana Date: 2015-06-20 18:07:53 +0000
20-06-2015

URL: http://hg.openjdk.java.net/jdk9/hs-comp/hotspot/rev/421989a11af8 User: roland Date: 2015-06-10 16:14:55 +0000
10-06-2015