From: Al Viro <viro@ftp.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Add __builtin_popcountl
Date: Thu, 26 Oct 2006 20:19:41 +0100 [thread overview]
Message-ID: <20061026191941.GK29920@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0610261153510.3962@g5.osdl.org>
On Thu, Oct 26, 2006 at 11:56:00AM -0700, Linus Torvalds wrote:
>
>
> 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.
Well... Keep in mind that those _are_ functions; i.e. unlike something
like __builtin_choose_expr() you can pass such puppy to a function
expecting a callback, etc.
So it's not enough to special-case them; we really need types for those
symbols. I don't think that it will be more efficient in the end.
prev parent reply other threads:[~2006-10-26 19:19 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
2006-10-26 19:19 ` Al Viro [this message]
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=20061026191941.GK29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).