Compilation results in either compiler thread stack overflow or with 
command-line switch -XssNm can result in OutOfMemory error.

Problem occurs during compilation of t1::main in program below:
// ------------------------------------------------------------
// t1.java
class c
{
    private int val;

    void setVal( int x )
    {
        this.val = x;
    }
}

public class t1
{

    public static void main( String[] args )
    {
        final int n = 100000000;

        for ( int i = 0; i < n; i++ ) {
            c aC = new c();
            aC.setVal( i );
        }
    }
}
// ------------------------------------------------------------

// WIN32 ===== Ladybird FCS

java -Xbatch t1
CRASH

java -Xbatch -Xss1m t1
OutOfMemory in CompileThread0

The product command line did not result in a crash on Solaris SPARC

// SPARC ===== Current merlin_beta2  

Assert in Node::verify_construction "Node limit exceeded" during loop unrolling.

1) Use a non-final value for the loop upper bound
2) split the loop into two loop nests with smaller bounds

In general, modify the loop bounds to avoid the overflow condition.

  xxxxx@xxxxx   2001-05-25

Checked this in debugger for current merlin_beta2 c2_baseline.

The heuristic for loop unrolling produces a result of -694967296 when a 
positive value is expected.


  xxxxx@xxxxx   2001-05-30

The fix has been putback to c2_baseline this afternoon.