From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Important per-cpu fix.
Date: 3 Sep 2002 21:52:45 -0700 [thread overview]
Message-ID: <al43it$mel$1@cesium.transmeta.com> (raw)
In-Reply-To: 20020904042036.816A62C1B6@lists.samba.org
Followup to: <20020904042036.816A62C1B6@lists.samba.org>
By author: Rusty Russell <rusty@rustcorp.com.au>
In newsgroup: linux.dev.kernel
>
> In message <20020903.195455.117344683.davem@redhat.com> you write:
> > From: Rusty Russell <rusty@rustcorp.com.au>
> > Date: Wed, 04 Sep 2002 12:35:41 +1000
> >
> > This might explain the wierd per-cpu problem reports from Andrew and
> > Dave, and also that nagging feeling that I'm an idiot...
> >
> > Verifying... no without the explicit initializers the per-cpu stuff
> > still ends up in the BSS with egcs-2.9X, even with your fix applied.
>
> OK. I really hate working around wierd toolchain bugs (I use 2.95.4
> here and it's fine), and adding an initializer to the macro is ugly.
>
> If you're not going to upgrade your compiler, will you accept a gcc
> patch to fix this? If so, where can I get the source to your exact
> version?
>
gcc puts all uninitialized variables in .bss, and it apparently can't
be overridden. This seems to be a side effect of the way gcc handles
common variables.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-09-04 4:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 2:35 [PATCH] Important per-cpu fix Rusty Russell
2002-09-04 2:54 ` David S. Miller
2002-09-04 4:04 ` Rusty Russell
2002-09-04 4:52 ` H. Peter Anvin [this message]
2002-09-09 8:06 ` Rusty Russell
2002-09-09 8:16 ` David S. Miller
2002-09-04 5:05 ` David S. Miller
2002-09-04 5:17 ` Linus Torvalds
2002-09-04 5:12 ` David S. Miller
2002-09-04 6:00 ` Rusty Russell
2002-09-04 6:06 ` David S. Miller
2002-09-04 6:19 ` David S. Miller
2002-09-04 7:38 ` Rusty Russell
2002-09-06 9:57 ` Pavel Machek
2002-09-09 3:45 ` Rusty Russell
2002-09-09 6:13 ` David S. Miller
2002-09-09 8:17 ` Rusty Russell
2002-09-09 8:15 ` David S. Miller
2002-09-09 20:58 ` Alan Cox
2002-09-09 21:06 ` Andrew Morton
2002-09-10 9:41 ` Rusty Russell
2002-09-04 15:44 ` Thunder from the hill
2002-09-04 23:18 ` David S. Miller
2002-09-04 2:56 ` Andrew Morton
2002-09-04 2:46 ` William Lee Irwin III
2002-09-04 3:42 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 9:10 Dipankar Sarma
2002-09-05 9:09 ` William Lee Irwin III
2002-09-05 19:08 ` Dipankar Sarma
2002-09-05 19:11 ` William Lee Irwin III
2002-09-09 12:17 Matthew Wilcox
2002-09-09 23:24 ` 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='al43it$mel$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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