All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: sparclinux@vger.kernel.org
Subject: GCC 4.2.1 produces broken 2.6.22.1 kernel.
Date: Mon, 06 Aug 2007 17:53:14 +0000	[thread overview]
Message-ID: <46B7600A.3060700@walrond.org> (raw)

Andrew Walrond wrote:
> 
> I've got a horrible feeling I've just spent a day fighting against a
> miscompilation by gcc-4.2.
> 
> Perhaps this is a known problem? I'm rebuilding with gcc-4.1.2 now and
> will report back shortly....
> 

Confirmed; GCC 4.2.1 (vanilla) produces a broken 2.6.22.1 kernel. I
don't know why, or whether GCC or the kernel is at fault, but the exact
same kernel and config builds and boots fine with GCC 4.1.2.

This is on a Sun T1000 niagra box. Anything I can do? let me know.

Andrew Walrond

             reply	other threads:[~2007-08-06 17:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 17:53 Andrew Walrond [this message]
2007-08-08  5:44 ` GCC 4.2.1 produces broken 2.6.22.1 kernel David Miller
2007-08-25  5:18 ` David Miller
2007-08-25  8:05 ` Andrew Walrond
2007-08-25  9:51 ` David Miller
2007-10-17 11:38 ` David Miller
2007-10-17 12:14 ` Andrew Walrond
2007-10-18  1:09 ` David Miller
2007-10-18  9:52 ` Andrew Walrond
2007-10-18 10:27 ` David Miller

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=46B7600A.3060700@walrond.org \
    --to=andrew@walrond.org \
    --cc=sparclinux@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.