[JDK9] RFR(XXS): JDK-8036576 - jtreg failed on Test6792161 timed out

Vladimir Kozlov vladimir.kozlov at oracle.com
Fri Mar 14 16:29:31 UTC 2014


Looks good.

We run our nightly testing with fastdebug VM only.

Thanks,
Vladimir

On 3/14/14 9:18 AM, S. Bharadwaj Yadavalli wrote:
> Please review the proposed change to timeout value for the test. The reasoning for the increase is as follows:
>
> When the test is run using fastdebug VM, it executes additional debug code. Verification of IR during Range Check
> Elimination phase of C1 compiler is one such additional debug code executed. The runtime complexity of verification step
> is non-linear. Specifically, the execution of this test forces compilation and sets an increased inlining size. The
> increased inlining size results in increased size of compilation units in (at least some) method compilations.
> Consequently, the IR verification consumes significant portion of runtime. Execution of the test using a fastdebug VM
> built with tip of hotspot-comp tree
>
> $ time ../hotspot-comp/build/solaris/jdk-solaris-sparcv9/fastdebug/bin/java -Xcomp -XX:MaxInlineSize=120 Test6792161
> real 4m19.321s
> user 4m19.636s
> sys 0m0.719s
>
> compared to that using hotspot built without the the above verification:
>
> $ time ../hotspot-comp/build/solaris/jdk-solaris-sparcv9/fastdebug/bin/java -Xcomp -XX:MaxInlineSize=120 Test6792161
>
> real 1m31.486s
> user 1m31.863s
> sys 0m0.743s
>
> So, it appears that the timeout value needs to be increased from 300 if we use fastdebug VM to run this test.
>
> Changeset at http://cr.openjdk.java.net/~bharadwaj/8036576/webrev_0/
> Bug report at https://bugs.openjdk.java.net/browse/JDK-8036576
>
> Thanks,
>
> Bharadwaj
>
>
>


More information about the hotspot-compiler-dev mailing list