All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: linux-next: ia64 allmodconfig
Date: Thu, 21 Aug 2008 23:32:02 +0000	[thread overview]
Message-ID: <20080821233202.GF8051@sgi.com> (raw)
In-Reply-To: <20080820233526.14c44ea6.akpm@linux-foundation.org>

On Thu, Aug 21, 2008 at 04:11:32PM -0700, Luck, Tony wrote:
> > Not sure if this is helpful, but google pointed me at:
> > http://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg116574.html
> 
> That said "Fixed in 4.0.0" ... so I grabbed and built a newer
> gcc (4.2.4) and lo and behold the next-20080821 tag builds
> and boots just fine[*] with it.
> 
> 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?
> 
> -Tony
> 
> [*] If you ignore that the 4.2.4 compiler is about 15% slower
> than my trusty old 3.4.6 :-(

I have been doing a bisect using akpm's compiler to see if I can find
the individual commit.  Unfortunately, my laptop isn't the fastest build
machine in the world.

I did objdump the built-in.o and there is no such symbol in that file.
'strings' agrees.

Thanks,
Robin

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

Thread overview: 17+ 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 [this message]
2008-08-21 23:39 ` Gerald Pfeifer
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
  -- strict thread matches above, loose matches on Subject: below --
2008-07-31  1:31 Andrew Morton
2008-07-31  9:59 ` Avi Kivity

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=20080821233202.GF8051@sgi.com \
    --to=holt@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.