From: Uros Bizjak <ubizjak@gmail.com>
To: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, i386]: Committed: Macroize s<cc> and b<cc> patterns
Date: Sat, 15 Mar 2008 11:18:00 -0000 [thread overview]
Message-ID: <47DBAFA3.2010807@gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0803150012310.12283@caipclassic.rutgers.edu>
Kaveh R. GHAZI wrote:
>> Index: i386.h
>> ===================================================================
>> --- i386.h (revision 133145)
>> +++ i386.h (working copy)
>> @@ -691,6 +691,10 @@
>> builtin_define ("__SSE_MATH__"); \
>> if (TARGET_SSE_MATH && TARGET_SSE2) \
>> builtin_define ("__SSE2_MATH__"); \
>> + \
>> + /* Define inline functions with immediate arguments. */ \
>> + if (optimize && !flag_keep_inline_functions) \
>> + builtin_define ("__SSE_USE_INLINED_FUNC__"); \
>> } \
>> while (0)
>>
>
>
> The i386.h hunk wasn't mentioned in the ChangeLog and doesn't seem related
> to this patch.
>
This part was present in posted diff only, not in the commit itself.
Uros.
prev parent reply other threads:[~2008-03-15 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 21:34 Uros Bizjak
2008-03-15 7:59 ` Kaveh R. GHAZI
2008-03-15 11:18 ` Uros Bizjak [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=47DBAFA3.2010807@gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).