From: Richard Biener <rguenther@suse.de>
To: Jeff Law <law@redhat.com>,gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][1/n][RFC] Make FRE/PRE somewhat predicate aware
Date: Fri, 16 May 2014 18:17:00 -0000 [thread overview]
Message-ID: <11a6594a-80ab-4119-91ce-2b2e1c3bdfc0@email.android.com> (raw)
In-Reply-To: <537645BF.9080807@redhat.com>
On May 16, 2014 7:07:11 PM CEST, Jeff Law <law@redhat.com> wrote:
>On 05/16/14 02:02, Richard Biener wrote:
>>>
>> Quiet as usual.
>Which strongly suggests folks trust you to do the right thing here :-)
> I think the FRE/PRE reference in $SUBJECT made me ignore the patch
>entirely -- my brain hurts when I look at our tree PRE implementation.
Heh, it's much easier to understand than it once was!
:)
Richard.
>Jeff
prev parent reply other threads:[~2014-05-16 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 11:51 Richard Biener
2014-05-16 8:04 ` Richard Biener
2014-05-16 17:07 ` Jeff Law
2014-05-16 18:17 ` Richard Biener [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=11a6594a-80ab-4119-91ce-2b2e1c3bdfc0@email.android.com \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).