-
Enhancement
-
Resolution: Fixed
-
P3
-
8, 9
-
b127
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8256952 | openjdk8u282 | Aleksey Shipilev | P3 | Resolved | Fixed | b04 |
In order to better test the concurrency support in JVM, we introduced StressLCM/StressGCM flags that randomize C2's instruction scheduling:
develop(bool, StressLCM, false, \
"Randomize instruction scheduling in LCM") \
\
develop(bool, StressGCM, false, \
"Randomize instruction scheduling in GCM") \
\
This, however, requires fastdebug build, which is not really fast for concurrency testing, as it does lots of asserts in VM codepaths (notably, GC). We would be better off turning these flags to diagnostic, to pop out in product builds.
develop(bool, StressLCM, false, \
"Randomize instruction scheduling in LCM") \
\
develop(bool, StressGCM, false, \
"Randomize instruction scheduling in GCM") \
\
This, however, requires fastdebug build, which is not really fast for concurrency testing, as it does lots of asserts in VM codepaths (notably, GC). We would be better off turning these flags to diagnostic, to pop out in product builds.
- backported by
-
JDK-8256952 Turn StressLCM/StressGCM flags to diagnostic
- Resolved
- relates to
-
JDK-8160761 [TESTBUG] Several compiler tests fail with product bits
- Resolved