-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b22
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8009955 | 8 | Unassigned | P4 | Resolved | Fixed | b81 |
JDK-8193049 | 7u181 | David Buck | P4 | Resolved | Fixed | b01 |
This improvement will greatly aid the concurrency testing.
The possible idea is:
- LCM schedules the instructions within the basic block, choosing the schedule based on the node inputs, latency, etc; we can hijack the selection process and randomize the choice.
- GCM selects the basic block up the dominator tree with the best latency to fit the Node in; we can hijack this and randomize the placement.
The possible idea is:
- LCM schedules the instructions within the basic block, choosing the schedule based on the node inputs, latency, etc; we can hijack the selection process and randomize the choice.
- GCM selects the basic block up the dominator tree with the best latency to fit the Node in; we can hijack this and randomize the placement.
- backported by
-
JDK-8009955 Fuzz instruction scheduling in HotSpot compilers
- Resolved
-
JDK-8193049 Fuzz instruction scheduling in HotSpot compilers
- Resolved
- duplicates
-
JDK-4738695 Compilation module stress testing
- Closed
- relates to
-
JDK-8007898 Incorrect optimization of Memory Barriers in Matcher::post_store_load_barrier()
- Resolved
-
JDK-8253765 C2: Control randomization in StressLCM and StressGCM
- Resolved