From: Richard Henderson <rth@twiddle.net>
To: davidm@hpl.hp.com
Cc: Arnd Bergmann <arnd@arndb.de>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-arch@vger.kernel.org, epasch@de.ibm.com, hare@suse.de
Subject: Re: static DEFINE_PER_CPU vs. modules
Date: Mon, 3 May 2004 11:01:56 -0700 [thread overview]
Message-ID: <20040503180156.GA10981@twiddle.net> (raw)
In-Reply-To: <16534.34396.940596.361864@napali.hpl.hp.com>
On Mon, May 03, 2004 at 10:50:20AM -0700, David Mosberger wrote:
> Seems to me this is a gcc bug if it
> generates code that is unable to reach all possible addresses.
Nope. There are multiple memory models for amd64. The default
assumes a 32-bit local data segment, since that makes for the
most efficient code generation and works virtually all of the time.
No different than assuming a 22-bit small-data section by default
for ia64...
r~
next prev parent reply other threads:[~2004-05-03 18:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 15:41 static DEFINE_PER_CPU vs. modules Arnd Bergmann
2004-05-03 17:50 ` David Mosberger
2004-05-03 18:01 ` Richard Henderson [this message]
2004-05-03 18:37 ` David Mosberger
2004-05-03 22:24 ` Arnd Bergmann
2004-05-03 23:12 ` David Mosberger
2004-05-04 8:56 ` Arnd Bergmann
2004-05-04 2:38 ` Andrew Morton
2004-05-04 14:17 ` Arnd Bergmann
2004-05-04 16:29 ` David Mosberger
2004-05-04 19:03 ` Andrew Morton
2004-05-04 19:15 ` David Mosberger
2004-05-04 19:23 ` Andrew Morton
2004-05-04 19:45 ` David Mosberger
2004-05-05 8:21 ` Arnd Bergmann
2004-05-05 8:29 ` Andrew Morton
2004-05-05 9:24 ` Arnd Bergmann
2004-05-05 9:33 ` Rusty Russell
2004-05-05 16:17 ` David Mosberger
2004-05-05 3:18 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2004-05-05 17:42 Martin Schwidefsky
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=20040503180156.GA10981@twiddle.net \
--to=rth@twiddle.net \
--cc=arnd@arndb.de \
--cc=davidm@hpl.hp.com \
--cc=epasch@de.ibm.com \
--cc=hare@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.