public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
* SPECjbb X86 validation failures
@ 2002-04-25  1:26 Boehm, Hans
  2002-04-25  3:03 ` Andrew Haley
  0 siblings, 1 reply; 2+ messages in thread
From: Boehm, Hans @ 2002-04-25  1:26 UTC (permalink / raw)
  To: 'tromey@redhat.com'; +Cc: 'java@gcc.gnu.org'

I'm unfortunately still seeing problems with SPECjbb on X86 with gcc3.1.
These are apparently optimization failures.  They don't seem to be
correlated with the reload1.c ICEs that I mentioned earlier.

I know that:

- They occur at -O1 and -O2, but not at -O0.

- The result is incorrect code, which is detected by the SPECjbb validation
test.

- More than one file in SPECjbb is misoptimized as a result.

- They do not occur on IA64.

I've identified one file that's definitely being misoptimized (by binary
search).  Are there known techniques for systematically narrowing this down
further?  I'm looking for something like a list of optimization flags
implied by -O1 that I can toggle individually, and ideally a flag to turn
off optimization in all functions past line N, or something similar.

The underying problem here is that this is a fairly large body of code,
which I don't understand well.  Thus tracking down a bug is hard, and
tracking down a misoptimization is harder.

Thanks.

Hans

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-04-25  9:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-25  1:26 SPECjbb X86 validation failures Boehm, Hans
2002-04-25  3:03 ` Andrew Haley

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).