RFR: 8059625 - JEP-JDK-8043304: Test task: DTrace- tests for segmented codecache feature

Christian Thalinger christian.thalinger at oracle.com
Mon Dec 22 22:17:55 UTC 2014

  40     public static int[] getAvailableCompilationLevels() {
  41         if (System.getProperty("java.vm.info").startsWith("interpreted ")) {
  42             return new int[0];
  43         }

Wouldn’t it be better to check the UseCompiler flag instead?

> On Dec 19, 2014, at 11:03 AM, Dmitrij Pochepko <dmitrij.pochepko at oracle.com> wrote:
> Hi all,
> Please review changes for https://bugs.openjdk.java.net/browse/JDK-8059625 -  JEP-JDK-8043304: Test task: DTrace- tests for segmented codecache feature
> Description: this fix introduce dtrace test, which verify that different combinations of available compile levels(and, in case compile levels allows it, different code heaps as result)  doesn't affect callstack shown by dtrace. There is a control class SegmentedCodeCacheDtraceTest.java and class for running via dtrace SegmentedCodeCacheDtraceTestWorker.java. A dtrace d script is also present (SegmentedCodeCacheDtraceTestScript.d). A control class is using DtraceRunner.java to run dtrace and then analyzing results using class SegmentedCodeCacheDtraceResultsAnalyzer with DtraceResultsAnalyzer interface.
> There is also a small class CompilerUtils.java created for usefull common code.
> webrev: http://cr.openjdk.java.net/~iignatyev/dpochepk/8059625/webrev.00/
> Additional note: Please note that this path assumes that fix for JDK-8066440 - Various changes in testlibrary for JDK-8059613 is also applied.
> Thanks,
> Dmitrij

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20141222/3edd1c9d/attachment-0001.html>

More information about the hotspot-compiler-dev mailing list