This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Java: Blank static final variable `TRUE' may not have be initialized.
- To: Tom Tromey <tromey at redhat dot com>
- Subject: Re: Java: Blank static final variable `TRUE' may not have be initialized.
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Wed, 13 Dec 2000 18:47:27 -0500
- Cc: Toon Moene <toon at moene dot indiv dot nluug dot nl>, gcc-bugs at gcc dot gnu dot org
- References: <3A37E48E.7EB8C148@moene.indiv.nluug.nl> <871yvb3n3v.fsf@creche.redhat.com>
On Wed, Dec 13, 2000 at 04:41:56PM -0700, Tom Tromey wrote:
> >>>>> "Toon" == Toon Moene <toon@moene.indiv.nluug.nl> writes:
>
> Toon> java/lang/Boolean.java:25: Blank static final variable `FALSE' may not
> Toon> have be initialized.
>
> This happens because (we think) gcj is miscompiled by the current cvs
> gcc. I believe Alex was planning to look at this.
Alex posted a temporary patch which fixes this, at least it worked for me.
It's at http://sources.redhat.com/ml/java-discuss/2000-12/msg00083.html
but I don't know whether applying it is now the Right Thing To Do; Alex
would have to speak to that point.
Note that if you apply the patch, you have to add the missing semicolon,
and re-bison.
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.