RFR (XS) 8156803: Turn StressLCM/StressGCM flags to diagnostic

[Vladimir Kozlov]

Looks good.

Thanks,
Vladimir

On 5/11/16 2:33 PM, Aleksey Shipilev wrote:
> Hi,
>
> 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") \
>
> These, however, require 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.
>
> Bug:
>    https://bugs.openjdk.java.net/browse/JDK-8156803
>
> Webrev:
>    http://cr.openjdk.java.net/~shade/8156803/webrev.01/
>
> Testing: manual testing with local x86_64/release build. I don't think
> we need to waste machine time on deeply testing this trivial change?
>
> Thanks,
> -Aleksey
>