From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Charles Arnold <CARNOLD@novell.com>
Subject: Re: [PATCH] x86-32: use __builtin_{memcpy,memset}
Date: Tue, 11 May 2010 13:33:04 +0100 [thread overview]
Message-ID: <4BE96AA002000078000024CB@vpn.id2.novell.com> (raw)
In-Reply-To: <C80F0671.13EE6%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 11.05.10 14:04 >>>
>What about this alternative version which distinguishes between GCC 4.3+
>(which should auto-inline quite sensibly) and earlier versions (which need
>help via macro mapping explicitly to __builtin_*)?
I don't think this will do what we expect in the presence of -fno-builtin
(see also my other response).
Jan
prev parent reply other threads:[~2010-05-11 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 9:05 [PATCH] x86-32: use __builtin_{memcpy,memset} Jan Beulich
2010-05-11 10:39 ` Keir Fraser
2010-05-11 12:04 ` Keir Fraser
2010-05-11 12:33 ` Jan Beulich [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=4BE96AA002000078000024CB@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=CARNOLD@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).