public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Reva Cuthbertson <reva@cup.hp.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ICE on IA-64 when compiling SPEC 2000 176.gcc at -O1
Date: Thu, 06 Dec 2001 12:57:00 -0000	[thread overview]
Message-ID: <3C0FDACE.B6D0759D@cup.hp.com> (raw)
In-Reply-To: <20011205231530.A9114@redhat.com>

Richard Henderson wrote:

> On Wed, Dec 05, 2001 at 05:07:50PM -0800, Reva Cuthbertson wrote:
> > ... and it happens because the born_index > death_index test fails so
> > we call abort().
>
> This is normally due to register life info being incorrect.
>
> That is, on input to local_alloc some register was reported
> to be set once and never die (certainly possible), yet the
> register does in fact die.
>
> Can't debug this further without a test case.
>
> r~

Richard,

     The problem can be seen when compiling the function
output_signed_leb128() in dwarfout.c in the gcc sources.
The function itself has been commented out on the main
branch so the problem does not happen if you compile
dwarfout.c with -O1.  However, the function output_signed_leb128()
is part of 176.gcc in SPEC 2000.  For convenience, I cut down
output_signed_leb128() into the following test case.  Compile
this with -O1 using gcc 3.1 for IA-64 and the internal compiler
error should occur.

static void
output_signed_leb128 (value)
     long value;
{
  int more;

  do
    {
      unsigned byte = (value & 0x7f);

      value >>= 7;
      if (((value == 0) && ((byte & 0x40) == 0))
          || ((value == -1) && ((byte & 0x40) == 1)))
        more = 0;
    }
  while (more);
}


Thanks!

Reva


      reply	other threads:[~2001-12-06 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 17:07 Reva Cuthbertson
2001-12-05 23:19 ` Richard Henderson
2001-12-06 12:57   ` Reva Cuthbertson [this message]

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=3C0FDACE.B6D0759D@cup.hp.com \
    --to=reva@cup.hp.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@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).