This is the mail archive of the
java-discuss@sources.redhat.com
mailing list for the Java project.
Re: -O2 failure with new ABI patches
- To: Bryce McKinlay <bryce at albatross dot co dot nz>
- Subject: Re: -O2 failure with new ABI patches
- From: Jeff Sturm <jeff dot sturm at appnet dot com>
- Date: Tue, 16 Jan 2001 09:58:53 -0500
- CC: java-discuss at sources dot redhat dot com
- Organization: Commerce One
- References: <3A637D28.9B0FF566@appnet.com> <3A63927C.C38C54C1@albatross.co.nz>
- Reply-To: jeff dot sturm at commerceone dot com
Bryce McKinlay wrote:
> IIRC, it seems to have something to do with the static allocated arrays.
Yes. Somehow -O2 drops the entire array initializer, causing an unreferenced
symbol.
> Are you sure this is a new ABI regression?
Either that or some recent patch. It definitely wasn't happening with my
previous gcc build. Also I had been building libjava using -O2 -fno-defer-pop
without incident.
> It goes away if you give the compiler class files to compile against (ie still
> compiling from .java source, but also having .class versions which the
> compiler uses for dependencies).
Hmm... I'm not seeing that. I'd expect it to go away when compiling bytecodes
however, since static arrays are then not possible.
--
Jeff Sturm
jeff.sturm@commerceone.com