From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Jeff Law <law@redhat.com>,gcc-patches@gcc.gnu.org
Subject: Re: [RFA] More type narrowing in match.pd V2
Date: Sat, 02 May 2015 21:18:00 -0000 [thread overview]
Message-ID: <B8D4208A-38D0-4387-92C7-DE3BC0EB01E6@gmail.com> (raw)
In-Reply-To: <55441BF2.60703@redhat.com>
On May 2, 2015 2:36:02 AM GMT+02:00, Jeff Law <law@redhat.com> wrote:
>Here's an updated patch to add more type narrowing to match.pd.
>
>Changes since the last version:
>
>Slight refactoring of the condition by using types_match as suggested
>by
>Richi. I also applied the new types_match to 2 other patterns in
>match.pd where it seemed clearly appropriate.
>
>Additionally the transformation is restricted by using the new
>single_use predicate. I didn't change other patterns in match.pd to
>use
>the new single_use predicate. But some probably could be changed.
>
>This (of course) continues to pass the bootstrap and regression check
>for x86-linux-gnu.
>
>There's still a ton of work to do in this space. This is meant to be
>an
>incremental stand-alone improvement.
>
>OK now?
I should find time to commit the already approved auto-wipe dump file patch.
So let's assume I'll get to it maybe next weekend and nobody will notice the 2 leftover .original dumps in this patch :)
Cheers,
next prev parent reply other threads:[~2015-05-02 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 0:36 Jeff Law
2015-05-02 21:18 ` Bernhard Reutner-Fischer [this message]
2015-05-04 17:05 ` Jeff Law
2015-05-04 9:02 ` Richard Biener
2015-05-04 19:59 ` H.J. Lu
2015-05-14 14:21 ` Marc Glisse
2015-05-14 14:47 ` Jeff Law
2015-05-18 9:22 ` Richard Biener
2015-05-18 9:48 ` Richard Biener
2015-05-18 12:40 ` Marc Glisse
2015-05-18 12:53 ` Richard Biener
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=B8D4208A-38D0-4387-92C7-DE3BC0EB01E6@gmail.com \
--to=rep.dot.nop@gmail.com \
--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).