request for review (XS)
David.Holmes at oracle.com
Fri Oct 8 19:05:30 PDT 2010
Karen Kinnear said the following on 10/09/10 06:07:
> Looks good.
> I could have sworn we added this years ago - but that a develop flag
> PrintJVMWarnings - which only appears to say whether you have
> used "deprecated?" JVM_XXX APIs. I wonder if you could change
> that flag to product and use it for all warnings?
Keith initially proposed that approach internally but it had some issues
because some of those "deprecated" JVM_XXX functions actually get called
- in particular the Compiler API functions get invoked by AWT code.
Because warnings are enabled by default, this would cause warnings to
appears for every app that uses the AWT.
Though with the current discussion regarding the "invisible VM" I'm
unclear whether the accepted approach is for warnings to be enabled by
default or not ???
> On Oct 8, 2010, at 2:35 PM, Keith McGuigan wrote:
>> New flag for turning off the printing of warnings:
>> webrev: http://cr.openjdk.java.net/~kamg/6392697/webrev.00/
>> - Keith
More information about the hotspot-runtime-dev