[13] RFR (S): 8217358: Optimized build is broken by Shenandoah changes

[Vladimir Ivanov]

Thanks for review, Aleksey.

>> Aside: does anyone use "optimized", and for what?
> 
> +1. It's the first I've heard of it. How does one even build that
> config?

Optimized build is something in-between product and fastdebug builds. 
There's some diagnostic code in HotSpot which isn't available in product 
builds. It may be useful to enable it, but without incurring all the 
costs of fastdebug. That's the difference between notproduct & develop 
flags and !PRODUCT & ASSERT #ifdefs.

As of now, It's enough to specify --with-debug-level=optimized to get it 
built. The plan is to eliminate optimized JDK build [1] and replace it 
with a JVM feature.

As for me, I use optimized to access C2-specific diagnostic 
features/output when I need them in release binaries (e.g., 
IdealGraphVisualizer, PrintEscapeAnalysis et all).

Best regards,
Vladimir Ivanov

[1] https://bugs.openjdk.java.net/browse/JDK-8202283