From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Can gcc 3.4 compile 2.6.6 kernel?
Date: Fri, 21 May 2004 18:15:58 +0000 [thread overview]
Message-ID: <20040521181558.GA6683@lucon.org> (raw)
In-Reply-To: <20040521170820.GA5516@lucon.org>
On Fri, May 21, 2004 at 11:09:52AM -0700, David Mosberger wrote:
> >>>>> On Fri, 21 May 2004 10:08:20 -0700, "H. J. Lu" <hjl@lucon.org> said:
>
> HJ> Has anyone tried to use gcc 3.4 to compile 2.6.6 kernel? I got many
> HJ> dependency violation messages from assembler and
>
> HJ> mm/memory.c: In function `copy_page_range':
> HJ> mm/memory.c:391: internal compiler error: in verify_local_live_at_start, at
> HJ> flow.c:546
> HJ> Please submit a full bug report,
> HJ> with preprocessed source if appropriate.
> HJ> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>
> I have been using a pre-release version of 3.4 with good success.
Can you show me your
# gcc -v
> I haven't had a need to switch to 3.4 final so far, so I haven't really
> tried it.
I filed a bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id\x15569
H.J.
next prev parent reply other threads:[~2004-05-21 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 17:08 Can gcc 3.4 compile 2.6.6 kernel? H. J. Lu
2004-05-21 18:00 ` Jesse Barnes
2004-05-21 18:09 ` David Mosberger
2004-05-21 18:15 ` H. J. Lu [this message]
2004-05-21 18:23 ` David Mosberger
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=20040521181558.GA6683@lucon.org \
--to=hjl@lucon.org \
--cc=linux-ia64@vger.kernel.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