From: Linus Torvalds <torvalds@osdl.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Add __builtin_popcountl
Date: Thu, 26 Oct 2006 11:56:00 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610261153510.3962@g5.osdl.org> (raw)
In-Reply-To: <20061026184301.GJ29920@ftp.linux.org.uk>
On Thu, 26 Oct 2006, Al Viro wrote:
>
> AFAICS, that's way over the top. That kind of stuff is needed only
> when builtin can't be described as a normal function. This, OTOH...
On the other hand, adding "true" builtin functions is actually a lot
cheaper than adding bogus code to be parsed explicitly.
So I'd actually prefer a way to have a table to describe and initialize
these things, as a way to make it a lot more efficient, and without the
silly preprocessor buffer hacks..
The preprocessor hack is certainly simple, but it's not what you really
want in real life.
Linus
next prev parent reply other threads:[~2006-10-26 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 17:47 [PATCH] Add __builtin_popcountl Matthew Wilcox
2006-10-26 18:43 ` Al Viro
2006-10-26 18:56 ` Linus Torvalds [this message]
2006-10-26 19:19 ` Al Viro
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=Pine.LNX.4.64.0610261153510.3962@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-sparse@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=viro@ftp.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).