public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gp@novell.com>
To: linux-ia64@vger.kernel.org
Subject: RE: linux-next: ia64 allmodconfig
Date: Thu, 21 Aug 2008 23:39:55 +0000	[thread overview]
Message-ID: <alpine.LSU.1.99.0808220133050.16120@enan.fvgr> (raw)
In-Reply-To: <20080820233526.14c44ea6.akpm@linux-foundation.org>

On Thu, 21 Aug 2008, Luck, Tony wrote:
> Still need to figure out exactly what broke the build with a 3.x gcc to 
> see if there is an easy workaround. Though 4.0.0 was released over three 
> years ago ... is it time to give up on the ancient 3.x technology?

Yes.  I've got a hard time seeing why anyone would use GCC 3.x to build 
current Linux kernels for Itanium (except when using an acient distro as
the base for kernel development).

> [*] If you ignore that the 4.2.4 compiler is about 15% slower
> than my trusty old 3.4.6 :-(

The resulting binary should be faster, though. ;-)  How about giving
GCC 4.3 a try, by the way?  IIRC, GCC 4.2 has some aliasing issues
that have been addressed.

Gerald

  parent reply	other threads:[~2008-08-21 23:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  6:35 linux-next: ia64 allmodconfig Andrew Morton
2008-08-21 12:59 ` Robin Holt
2008-08-21 13:04 ` Robin Holt
2008-08-21 16:30 ` Andrew Morton
2008-08-21 20:14 ` Luck, Tony
2008-08-21 21:08 ` Robin Holt
2008-08-21 23:11 ` Luck, Tony
2008-08-21 23:32 ` Robin Holt
2008-08-21 23:39 ` Gerald Pfeifer [this message]
2008-08-22  0:23 ` Luck, Tony
2008-08-22  3:29 ` Robin Holt
2008-08-22  3:31 ` Robin Holt
2008-08-22  8:00 ` Pekka Enberg
2008-08-22 13:03 ` Robin Holt
2008-08-22 23:34 ` Luck, Tony

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=alpine.LSU.1.99.0808220133050.16120@enan.fvgr \
    --to=gp@novell.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