public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at specifixinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/15569] [3.4 regression] Gcc 3.4.1 failed to build ia64 2.6.6 kernel
Date: Tue, 01 Jun 2004 04:20:00 -0000	[thread overview]
Message-ID: <20040601042009.15045.qmail@sourceware.org> (raw)
In-Reply-To: <20040521181217.15569.hjl@lucon.org>


------- Additional Comments From wilson at specifixinc dot com  2004-06-01 04:20 -------
Subject: Re:  [3.4 regression] Gcc 3.4.1 failed to build
 ia64 2.6.6 kernel

hjl at lucon dot org wrote:
> [hjl@gnu-4 linux-2.6.6]$ /usr/gcc-3.4/bin/gcc	 -frename-registers -O2  
> -mconstant-gp -c foo.c
> foo.c: In function `ext2_lookup':
> foo.c:66: internal compiler error: in verify_local_live_at_start, at flow.c:546

When -frename-registers got added to -O2 on mainline, there were IA-64 
bootstrap failures.  I had to write a patch for that.  The patch can be 
found here:
     http://gcc.gnu.org/ml/gcc-patches/2004-04/msg01328.html

With this patch applied, the testcase compiles OK.

So it looks like we need to backport this patch onto the gcc-3.4 branch. 
  I am leaving for the GCC Summit tomorrow, so I won't be able to test 
this until next week.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15569


  parent reply	other threads:[~2004-06-01  4:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 18:43 [Bug target/15569] New: " hjl at lucon dot org
2004-05-22 18:45 ` [Bug target/15569] " hjl at lucon dot org
2004-05-22 19:17 ` pinskia at gcc dot gnu dot org
2004-05-22 19:21 ` hjl at lucon dot org
2004-05-22 21:44 ` hjl at lucon dot org
2004-05-22 21:47 ` pinskia at gcc dot gnu dot org
2004-05-23 21:50 ` hjl at lucon dot org
2004-05-23 22:04 ` pinskia at gcc dot gnu dot org
2004-05-23 22:20 ` hjl at lucon dot org
2004-05-23 22:46 ` pinskia at gcc dot gnu dot org
2004-05-23 22:48 ` hjl at lucon dot org
2004-05-23 22:56 ` pinskia at gcc dot gnu dot org
2004-05-23 22:57 ` hjl at lucon dot org
2004-05-28  1:44 ` bonzini at gnu dot org
2004-06-01  4:20 ` wilson at specifixinc dot com [this message]
2004-06-01  4:24 ` wilson at gcc dot gnu dot org
2004-06-08  6:57 ` cvs-commit at gcc dot gnu dot org
2004-06-08  6:58 ` wilson at gcc dot gnu dot org
2004-06-08  6:59 ` wilson at gcc dot gnu dot org
2004-06-10  8:43 ` cvs-commit at gcc dot gnu dot org
2004-06-10  8:46 ` cvs-commit at gcc dot gnu dot org
2004-06-28 22:34 ` cvs-commit at gcc dot gnu dot org
2004-07-01 10:52 ` cvs-commit at gcc dot gnu dot org

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=20040601042009.15045.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).