From: Andrew Walrond <andrew@walrond.org>
To: sparclinux@vger.kernel.org
Subject: Re: GCC 4.2.1 produces broken 2.6.22.1 kernel.
Date: Thu, 18 Oct 2007 09:52:43 +0000 [thread overview]
Message-ID: <47172CEB.6010300@walrond.org> (raw)
In-Reply-To: <46B7600A.3060700@walrond.org>
David Miller wrote:
>
> I just have done some SMP kernel testing on my Niagara-2 systems
> and it looks really good with that gcc-4.2.x patch I posted.
> -
Excellent. I'll give it a whirl here aswell.
Will you be posting the patch to the gcc ML? My little distro is
wonderfully symmetric across x86/x86_64/itanium2/sparc64 except for the
need to use gcc 4.1 on sparc64, so it will be a nice to get a fix merged
for 4.2.3 and 4.3/mainline.
And how are those Niagara2 systems shaping up? Much improvement over
Niagara1 ?
Andrew Walrond
next prev parent reply other threads:[~2007-10-18 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 17:53 GCC 4.2.1 produces broken 2.6.22.1 kernel Andrew Walrond
2007-08-08 5:44 ` 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 [this message]
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=47172CEB.6010300@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.