public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Boehm, Hans" <hans_boehm@hp.com>
To: "'tromey@redhat.com'" <tromey@redhat.com>
Cc: "'java@gcc.gnu.org'" <java@gcc.gnu.org>
Subject: SPECjbb X86 validation failures
Date: Thu, 25 Apr 2002 01:26:00 -0000	[thread overview]
Message-ID: <40700B4C02ABD5119F000090278766443BF23F@hplex1.hpl.hp.com> (raw)

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

             reply	other threads:[~2002-04-25  5:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25  1:26 Boehm, Hans [this message]
2002-04-25  3:03 ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40700B4C02ABD5119F000090278766443BF23F@hplex1.hpl.hp.com \
    --to=hans_boehm@hp.com \
    --cc=java@gcc.gnu.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).