RFR: 8152104: G1 StringTable cleaning incorrectly logs with the stringdedup tag

Stefan Johansson stefan.johansson at oracle.com
Fri Mar 18 09:35:23 UTC 2016


Looks good,
StefanJ

On 2016-03-18 10:15, Stefan Karlsson wrote:
> Hi all,
>
> There's a test that needs to be updated as well. Please review this 
> test patch:
>
> $ hg diff test/ -r -2
> diff --git a/test/gc/g1/TestStringSymbolTableStats.java 
> b/test/gc/g1/TestStringSymbolTableStats.java
> --- a/test/gc/g1/TestStringSymbolTableStats.java
> +++ b/test/gc/g1/TestStringSymbolTableStats.java
> @@ -39,7 +39,7 @@
>
>      ProcessBuilder pb = 
> ProcessTools.createJavaProcessBuilder("-XX:+UseG1GC",
> "-XX:+UnlockExperimentalVMOptions",
> - "-Xlog:gc+stringdedup=trace",
> + "-Xlog:gc+stringtable=trace",
> SystemGCTest.class.getName());
>
>      OutputAnalyzer output = new OutputAnalyzer(pb.start());
>
> Thanks,
> StefanK
>
> On 2016-03-17 14:53, Stefan Karlsson wrote:
>> Hi all,
>>
>> Please review this small patch to change the log tag and level for 
>> the StringTable cleaning phase in G1.
>>
>> http://cr.openjdk.java.net/~stefank/8152104/webrev.00/
>> https://bugs.openjdk.java.net/browse/JDK-8152104
>>
>> Thanks,
>> StefanK
>



More information about the hotspot-gc-dev mailing list