From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Back to the future: which gcc for kernel 2.4.18 ?
Date: Wed, 05 Jun 2002 17:34:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905643@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905641@msgid-missing>
>>>>> On Wed, 5 Jun 2002 17:28:54 +0200 (DFT), Xavier Bru <Xavier.Bru@bull.net> said:
Xavier> Building kernel 2.4.18 for ia64 with gcc version 2.96
Xavier> 20000731 , it seems that there is some problem with code
Xavier> generation in the ia64_log_rec_header_print() routine that
Xavier> prints MCA informations: year appears to be 18002 :-)
Xavier> Looking at the code with gdb, it seems that the generated
Xavier> code uses the f6 register without ininitializing: ...
Xavier> 0xe0000000044351f1 <ia64_log_rec_header_print+337>: xmpy.l
Xavier> f6ö,f7 ...
Yes, I just tried with gcc 2.96 and I see this too: f6 is used twice
without being initialized anywhere in the routine.
Xavier> I tried using gcc3 (gcc version 3.0.2 20010905), but I get
Xavier> an internal compiler error when I build the kernel.
Haven't tried 3.0.2, but gcc3.1 compiles the code fine and without the
"f6-bug" (but this may be just luck, because gcc3.1 doesn't use xma at
all for this routine).
Can you narrow down the bug and report it to the gcc folks? It would
be good to know that gcc3.1 really gets it right (and doesn't just get
lucky).
--david
next prev parent reply other threads:[~2002-06-05 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 15:28 [Linux-ia64] Back to the future: which gcc for kernel 2.4.18 ? Xavier Bru
2002-06-05 17:34 ` David Mosberger [this message]
2002-06-13 23:40 ` Jim Wilson
2002-06-14 11:41 ` Xavier Bru
2002-06-14 17:04 ` Jim Wilson
2002-06-14 21:17 ` [Linux-ia64] Back to the future: which gcc for kernel 2.4.18 Wichmann, Mats D
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=marc-linux-ia64-105590701905643@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--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