HotSpot 1.3 fcs K,L,M fail against various JCK 1.2a and 1.2.2 tests, when
these tests are executed under WinNT in -Xcomp mode and are stressed-out
by JCK-stress tests belonging to the 'testbase_nsk' testbase.

This testbase_nsk is located at the directory:
    /net/sqesvr/vsn/testbase/testbase_nsk
and the tests are located in the subdirectory:
    ${TESTBASE_NSK}/src

Totally, 4 stress-tests based on JCK 1.2a, and 6 stress-tests based
on JCK 1.2.2 have failed:
    nsk/stress/jck12a/jck12a001
    nsk/stress/jck12a/jck12a002
    nsk/stress/jck12a/jck12a003
    nsk/stress/jck12a/jck12a004
    nsk/stress/jck12a/jck122003
    nsk/stress/jck12a/jck122004
    nsk/stress/jck12a/jck122008
    nsk/stress/jck12a/jck122010
    nsk/stress/jck12a/jck122011
    nsk/stress/jck12a/jck122012

To execute these tests you need to have the following stuff in the CLASSPATH:
    /usr/local/java/sqe-tools2.0/javatest.jar
    /usr/local/java/jck1.2/JCK-runtime-lang-12a/classes (needed only for tests: jck12a001-004)
    /usr/local/java/jck1.2.2/JCK-runtime-lang-122/classes (needed only for tests: jck122001-006)
    /usr/local/java/jck1.2.2/JCK-runtime-lang-122/classes (needed only for tests: jck122007-013)
Also, it is necessary to compile the stress-wrapper:
    ${TESTBASE_NSK}/src/nsk/stress/share/StressTest.java
and append its binary to the CLASSPATH.

Note, that some JCK tests need '-Xfuture' or '-verify' option to run correctly;
so you need to set '-verify' option to execute the JCK-stress tests, e.g:
    java -Xcomp -verify jck122004 2>log

Following is the list of primary JCK 1.2a and JCK 1.2.2 tests
involved into the stress testing:
jck12a001:
    javasoft.sqe.tests.lang.dasg060.dasg06001.dasg06001
jck12a002:
    javasoft.sqe.tests.lang.expr146.expr14602.expr14602
jck12a003:
    javasoft.sqe.tests.lang.type044.type04401.type04401
jck12a004:
    javasoft.sqe.tests.lang.fpl007.fpl00702m1.fpl00702m1
    javasoft.sqe.tests.lang.fpl007.fpl00702m1.fpl00702m2
jck122003:
    javasoft.sqe.tests.lang.expr146.expr14602.expr14602
    javasoft.sqe.tests.lang.expr229.expr22901.expr22901
    javasoft.sqe.tests.lang.expr238.expr23801.expr23801
jck122004:
    javasoft.sqe.tests.lang.expr288.expr28801.expr28801
    javasoft.sqe.tests.lang.expr346.expr34601.expr34601
    javasoft.sqe.tests.lang.expr468.expr46801.expr46801
    javasoft.sqe.tests.lang.expr482.expr48201.expr48201
    javasoft.sqe.tests.lang.expr491.expr49101.expr49101
    javasoft.sqe.tests.lang.expr491.expr49102.expr49102
jck122008:
    javasoft.sqe.tests.vm.iaload.iaload007.iaload00701.iaload00701
    javasoft.sqe.tests.vm.ineg.ineg001.ineg00101.ineg00101
    javasoft.sqe.tests.vm.ineg.ineg002.ineg00201.ineg00201
    javasoft.sqe.tests.vm.ineg.ineg004.ineg00401.ineg00401
    javasoft.sqe.tests.vm.isub.isub003.isub00301.isub00301
jck122010:
    javasoft.sqe.tests.vm.invokeinterface.invokeinterface022.invokeinterface02201.invokeinterface02201
jck122011:
    javasoft.sqe.tests.vm.saload.saload007.saload00701.saload00701
jck122012:
    javasoft.sqe.tests.vm.concepts.methods006.methods00601.methods00601

Note, that those primary JCK tests do not belong to exclude lists and look correct.
The mentioned JCK-stress tests were used to test HS 1.0, 1.0.1, 2.0 and 1.3 earlier,
and the problem only arises for recent builds of HS 1.3 (win32) in -Xcomp mode.

So, I believe that these failures are caused by some problem with Compiler1
arising in stress comditions.