From: Rusty Russell <rusty@rustcorp.com.au>
To: Adrian Bunk <bunk@kernel.org>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: initialization of static per-cpu variables
Date: Sun, 25 May 2008 20:35:24 +1000 [thread overview]
Message-ID: <200805252035.24535.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080523142904.GB28257@cs181133002.pp.htv.fi>
On Saturday 24 May 2008 00:29:04 Adrian Bunk wrote:
> On Thu, May 22, 2008 at 06:20:06PM +1000, Rusty Russell wrote:
> > Yep, it was an old toolchain used by Sparc: DaveM found this one. As you
> > say, it's ancient: I'm happy to queue a cleanup patch now everyone is on
> > a modern compiler.
>
> The commit says:
>
> GCC3.1 apparently gets confused about uninitialized sections
>
> We do still support gcc 3.2 (which is the same as 3.1 except for a C++
> ABI change) as a compiler for the kernel.
Adrian, that's a little silly. There are obviously bug fixes in 3.2 over
3.1.0. Noone has complained about the introduction of multiple other cases
which would screw things up if they experienced this bug.
Finally, it's a sparc64 problem and DaveM acked already. That's half the
userbase!
Cheers,
Rusty.
next prev parent reply other threads:[~2008-05-25 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 18:28 initialization of static per-cpu variables Vegard Nossum
2008-05-22 8:20 ` Rusty Russell
2008-05-22 16:12 ` David Miller
2008-05-23 14:29 ` Adrian Bunk
2008-05-23 14:43 ` Vegard Nossum
2008-05-25 10:35 ` Rusty Russell [this message]
2008-06-02 7:59 ` Adrian Bunk
2008-06-02 23:11 ` Rusty Russell
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=200805252035.24535.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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.