JDK-8342047 : Create Template Assertion Predicates with Halt nodes only instead of uncommon traps
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 24
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2024-10-14
  • Updated: 2024-10-14
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 24
24Unresolved
Related Reports
Blocks :  
JDK-8342043 - Split Opaque4Node into OpaqueTemplateAssertionPredicateNode and OpaqueNotNullNode
Blocks :  
JDK-8341977 - Replace predicate walking and cloning code with new predicate iterator and visitors
Description
We currently create Template Assertion Predicates with UCT out of convenience and to reuse existing Loop Predication code. This creates some problems down the line when we need to pattern match these and create copies of the templates when splitting a loop. 

After JDK-8341977 goes in, we have a unified way to iterate over predicates which enables us to easily replace UCTs with Halt nodes. The only thing left is to be able to unique identify Template Assertion Predicates which still could be confused with non null checks for intrinsics. JDK-8342043 will fix this. 

So, once JDK-8341977 and JDK-8342043 are in, we are good to go with this refactoring.