From: Jeff Garzik <jgarzik@pobox.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Arjan van de Ven <arjanv@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BK+PATCH] remove __constant_memcpy
Date: Thu, 17 Apr 2003 19:10:36 -0400 [thread overview]
Message-ID: <3E9F346C.8070406@pobox.com> (raw)
In-Reply-To: <20030417225850.GA17476@werewolf.able.es>
J.A. Magallon wrote:
> On 04.17, Jeff Garzik wrote:
>
>>On Thu, Apr 17, 2003 at 09:07:45AM -0700, Linus Torvalds wrote:
>
> [...]
>
>> #define memcpy(t, f, n) \
>> (__builtin_constant_p(n) ? \
>> __constant_memcpy3d((t),(f),(n)) : \
>> __memcpy3d((t),(f),(n)))
>>
>
>
> Do you know if this is more efficient ? :
>
> __builtin_choose_expr(__builtin_constant_p(n), ... , ....)
>
> Perhaps ?: reaches runtime, and __builtin doesn't.
No. The existing code (quoted above) is properly evaluated at
compile-time...
Jeff
next prev parent reply other threads:[~2003-04-17 22:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 0:57 [BK+PATCH] remove __constant_memcpy Jeff Garzik
2003-04-17 1:04 ` Jeff Garzik
2003-04-17 2:06 ` Linus Torvalds
2003-04-17 8:46 ` Arjan van de Ven
2003-04-17 9:02 ` Roman Zippel
2003-04-17 9:04 ` Arjan van de Ven
2003-04-17 9:11 ` Jakub Jelinek
2003-04-17 16:07 ` Linus Torvalds
2003-04-17 19:07 ` Jeff Garzik
2003-04-17 19:19 ` Jeff Garzik
2003-04-17 19:54 ` Linus Torvalds
2003-04-17 23:49 ` Jeff Garzik
2003-04-17 23:52 ` Jeff Garzik
2003-04-17 23:59 ` Linus Torvalds
2003-04-18 0:29 ` H. Peter Anvin
2003-04-18 9:06 ` Arjan van de Ven
2003-04-18 14:31 ` Timothy Miller
2003-04-18 15:07 ` Richard B. Johnson
2003-04-17 22:58 ` J.A. Magallon
2003-04-17 23:10 ` Jeff Garzik [this message]
2003-04-17 13:17 ` Alan Cox
2003-04-17 13:17 ` Alan Cox
2003-04-17 14:32 ` Jeff Garzik
2003-04-17 14:40 ` Jeff Garzik
2003-04-17 20:01 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-04-17 2:22 Nakajima, Jun
2003-04-17 23:50 Chuck Ebbert
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=3E9F346C.8070406@pobox.com \
--to=jgarzik@pobox.com \
--cc=arjanv@redhat.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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