From: Jeff Law <law@redhat.com>
To: Michael Collison <michael.collison@linaro.org>,
Richard Biener <richard.guenther@gmail.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Optimize certain end of loop conditions into min/max operation
Date: Fri, 31 Jul 2015 19:10:00 -0000 [thread overview]
Message-ID: <55BBBE2E.1020408@redhat.com> (raw)
In-Reply-To: <55BBBBE6.2070207@linaro.org>
On 07/31/2015 12:18 PM, Michael Collison wrote:
> Hi Jeff,
>
> Yes I will create a test case. I'm not quite sure what to check for even
> in the machine dependent test case. It's quite possible for the
> instructions that are generated to change over time.
I think we're going to want to look at the gimple IR and search for the
MIN/MAX expressions rather than the instructions. Given we don't know
where the transformation is going to land (yet), you can probably start
with -fdump-tree-optimized and scanning the .optimized dump.
We can still do that and have the test be target specific.
jeff
next prev parent reply other threads:[~2015-07-31 18:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 4:23 Michael Collison
2015-07-27 7:36 ` Bin.Cheng
2015-07-27 8:11 ` Bin.Cheng
2015-07-27 9:47 ` Richard Biener
2015-07-27 16:25 ` Jeff Law
2015-07-28 7:59 ` Richard Biener
2015-07-29 22:38 ` Michael Collison
2015-07-31 16:40 ` Jeff Law
2015-07-31 18:48 ` Michael Collison
2015-07-31 19:10 ` Jeff Law [this message]
2015-08-03 7:34 ` Richard Biener
2015-09-18 7:00 ` Michael Collison
2015-09-18 7:38 ` Marc Glisse
2015-09-18 7:41 ` Marc Glisse
2015-09-18 10:06 ` Richard Biener
2015-09-30 8:08 ` Michael Collison
2015-09-30 9:10 ` Richard Biener
2015-09-30 16:51 ` Michael Collison
2015-09-30 21:12 ` Marc Glisse
2015-10-01 5:40 ` Michael Collison
2015-10-01 6:42 ` Marc Glisse
2015-10-01 7:59 ` Michael Collison
2015-10-01 8:05 ` Marc Glisse
2015-10-01 8:21 ` Michael Collison
2015-10-06 9:21 ` Richard Biener
2015-09-18 22:01 ` Michael Collison
2015-09-18 22:09 ` Marc Glisse
2015-08-05 16:08 ` Alan Lawrence
2015-08-05 16:15 ` Jeff Law
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=55BBBE2E.1020408@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=michael.collison@linaro.org \
--cc=richard.guenther@gmail.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).