Re: Has anyone seen this build error before?

[Mo DeJong <mdejong at cygnus dot com>]

On Mon, 20 Nov 2000, Mo DeJong wrote:

> > The biggest problem for us is that the constant expression code in gcj
> > is very underpowered.  There are a lot of cases it doesn't handle, and
> > it is only used for declarations (and not, as far as I could tell,
> > case labels).
> 
> Boy, that is going to be a problem. Using the constant expression
> feature of a switch statement seems to be the best way to test
> compile time constants. It is used all over the place in Jacks.
> 
> > We also fail all of the "@" tests since I haven't had time to change
> > the test suite to add a constraint covering that case.  There are
> > around 10 of these.

Whooh! Got a working build of gcj! Reverting the string buffer
thing fixed it.

I added that constraint and reran the current compile tests.
Here are the numbers I am now seeing.

gcj:    Total   754     Passed  674     Skipped 15      Failed  65
Number of tests skipped for each constraint:
        14      atfiles
        1       pc

It looks like about 12 of these marked as "Failed" may just
be a problem in the test suite. Still gcj is not doing bad
at all. Most of the problems appear to be with final
variables and constant expressions in switch statements.

cheers
Mo DeJong
Red Hat Inc