United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6810855 KILL vs. TEMP ordering restrictions are too strong
JDK-6810855 : KILL vs. TEMP ordering restrictions are too strong

Details
Type:
Bug
Submit Date:
2009-02-26
Status:
Resolved
Updated Date:
2010-04-02
Project Name:
JDK
Resolved Date:
2009-03-18
Component:
hotspot
OS:
solaris_9
Sub-Component:
compiler
CPU:
sparc
Priority:
P4
Resolution:
Fixed
Affected Versions:
hs15
Fixed Versions:
hs15 (b03)

Related Reports
Backport:
Backport:
Relates:

Sub Tasks

Description
The support for TEMP operands in the adlc has some sanity checks that require TEMPs to come before KILLs since kill normally aren't really uses.  This simplifies some of the logic for mapping between operands and inputs.  The existing logic is being too strict since it complains about USE_KILLs instead of just raw KILLs.  The code should be modified to ignore USE_KILLs.

                                    

Comments
EVALUATION

this description is correct.
                                     
2009-02-26
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/ed6404fac86b
                                     
2009-02-27



Hardware and Software, Engineered to Work Together