public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Back to the future: which gcc for kernel 2.4.18 ?
Date: Thu, 13 Jun 2002 23:40:48 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905673@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905641@msgid-missing>

>Building kernel 2.4.18 for ia64 with gcc version 2.96 20000731 , it
>seems that there is some problem with code generation in the 
>ia64_log_rec_header_print() routine that prints MCA informations:
>year appears to be 18002 :-)
>Looking at the code with gdb, it seems that the generated code uses
>the f6 register without ininitializing:

I've tracked this down to a reload (register allocator) problem.  It looks
to be very rare, and it looks like it is still present in current gcc sources.
However, I'm not sure about that at the moment, as there are many possible
solutions, and it is possible someone implemented a non-obvious one.  I'm
continuing to look at this.  I want to try to reproduce it with current gcc
sources before I try to fix it.

>I tried using gcc3 (gcc version 3.0.2 20010905), but I get an internal 
>compiler error when I build the kernel.

I don't know what compiler you are refering to.  That doesn't look like an FSF
version number, and I don't know of any Red Hat compiler release with that
version number.

In any case, gcc 3.0 for IA-64 is not very interesting.  It wasn't adopted by
anybody that I know of for various reasons, so it never got stress tested and
is unlikely to be reliable.  Use gcc 3.1 instead.

Jim


  parent reply	other threads:[~2002-06-13 23:40 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
2002-06-13 23:40 ` Jim Wilson [this message]
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-105590701905673@msgid-missing \
    --to=wilson@redhat.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