-
Bug
-
Resolution: Fixed
-
P4
-
17, 18
-
b17
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8298922 | 17.0.7-oracle | Tobias Hartmann | P4 | Resolved | Fixed | b01 |
| JDK-8279373 | 17.0.3 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
I was puzzled by it when fixing JDK-8274060. It looks that new optimizations added by JDK-8273454 and JDK-8263006 rewire in(1) and in(2) in MulNode::Ideal, which means the chained transformations should see them? Yet, both inputs and their Type-s are cached locally and not refreshed. I have not seen failures due to this yet, but it looks that the current code is subtly incorrect because of this.
- backported by
-
JDK-8279373 C2: MulNode::Ideal chained transformations may act on wrong nodes
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8263006 Add optimization for Max(*)Node and Min(*)Node
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/256356d4
-
Commit
openjdk/jdk/756d22c3
-
Review
openjdk/jdk17u-dev/25
-
Review
openjdk/jdk/5631
(3 links to)