public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: John Ruttenberg <rutt@chezrutt.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/9382: AIX 5.2 ../../gcc-20030120/gcc/libgcc2.c:1161: internal compiler error: in extract_insn, at recog.c:2175
Date: Mon, 24 Mar 2003 17:26:00 -0000	[thread overview]
Message-ID: <20030324171600.17281.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/9382; it has been noted by GNATS.

From: John Ruttenberg <rutt@chezrutt.com>
To: gcc-gnats@gcc.gnu.org, glebourgeois@amadeus.net, gcc-bugs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/9382: AIX 5.2 ../../gcc-20030120/gcc/libgcc2.c:1161: internal compiler error: in extract_insn, at recog.c:2175
Date: Mon, 24 Mar 2003 12:11:12 -0500

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9382
 
 I have some more information about this.  It seems to happen or not depending
 on which compiler I use to bootstrap.  With 3.2.1 (binary from UCLA) and 2.9
 (binary form IBM), I encounter the problem.  With 2.95.3 (I bootstrapped), I
 do not encounter the problem.
 
 The fact that the problem can be reproduced with two different bootstrap
 compilers from such different releases leads me to suspect that perhaps there
 is some uninitialized variable involved.  Or some other cause of undefined
 behavior.
 
 I don't know that much aboug gcc internals, but perhaps I can narrow down a
 little further somehow.  But it will be time consuming and it would be good to
 know if anyone knows anything about this before I expend any energy on it.


             reply	other threads:[~2003-03-24 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 17:26 John Ruttenberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17  7:04 giovannibajo
2003-05-08  6:06 Dara Hazeghi
2003-01-21 11:36 glebourgeois

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=20030324171600.17281.qmail@sources.redhat.com \
    --to=rutt@chezrutt.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).