From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>,
"Steven N. Hirsch" <shirsch@adelphia.net>,
linux-kernel@vger.kernel.org
Subject: Re: Adaptec AIC7XXX v 6.0.6 BETA Released
Date: Thu, 14 Dec 2000 18:45:17 +0100 [thread overview]
Message-ID: <20001214184517.A19948@gruyere.muc.suse.de> (raw)
In-Reply-To: <200012140356.eBE3u8s42047@aslan.scsiguy.com> <E146VPa-00044k-00@the-village.bc.nu>
In-Reply-To: <E146VPa-00044k-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 14, 2000 at 10:14:51AM +0000
On Thu, Dec 14, 2000 at 10:14:51AM +0000, Alan Cox wrote:
> > I'll update my patch tomorrow to restore the definition of current.
> > I do fear, however, that this will perpetuate the polution of the
> > namespace should "current" ever get cleaned up.
>
> It can probably get cleaned up after 2.4 by making current() the actual
> inline. For 2.2 it won't change. Consider it a feature.
>
> It was done originally because the 2.0 code using #define based current
> generated better code than using inline functions. 2.2 upwards use a different
> (far nicer) method to find current.
The macro is still likely to generate better code. All released
gcc versions have the "inline penalty" causing bad register allocation
(maybe it'll be fixed with gcc 3's tree inliner)
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-14 18:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 22:15 Justin T. Gibbs
2000-12-14 1:31 ` Steven N. Hirsch
2000-12-14 3:56 ` Justin T. Gibbs
2000-12-14 4:22 ` David S. Miller
2000-12-14 4:57 ` Justin T. Gibbs
2000-12-14 10:18 ` Alan Cox
2000-12-14 14:03 ` Justin T. Gibbs
2000-12-14 15:53 ` Martin Dalecki
2000-12-14 15:10 ` Justin T. Gibbs
2000-12-14 16:15 ` Martin Dalecki
2000-12-14 17:56 ` Alan Cox
2000-12-14 19:26 ` Gérard Roudier
2000-12-14 10:14 ` Alan Cox
2000-12-14 13:59 ` Justin T. Gibbs
2000-12-14 15:03 ` Steven N. Hirsch
2000-12-14 15:07 ` Justin T. Gibbs
2000-12-14 17:03 ` Matthew Jacob
2000-12-14 17:54 ` Alan Cox
2000-12-14 18:02 ` Justin T. Gibbs
2000-12-14 18:38 ` Alan Cox
2000-12-14 18:05 ` Alan Cox
2000-12-14 17:45 ` Andi Kleen [this message]
2000-12-14 18:35 ` Alan Cox
2000-12-14 12:26 ` Steven N. Hirsch
2000-12-14 10:22 ` J . A . Magallon
2000-12-14 13:45 ` Justin T. Gibbs
2000-12-14 14:13 ` J . A . Magallon
2000-12-14 15:48 ` Christoph Hellwig
2000-12-14 16:24 ` Justin T. Gibbs
2000-12-30 16:31 ` Steven N. Hirsch
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=20001214184517.A19948@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shirsch@adelphia.net \
/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
all inboxes | Powered by JetHome®