From: Jakub Jelinek <jakub@redhat.com>
To: Sudi Das <Sudi.Das@arm.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>
Subject: Re: [PATCH][GCC] Simplification of 1U << (31 - x)
Date: Tue, 26 Sep 2017 13:06:00 -0000 [thread overview]
Message-ID: <20170926130612.GR1701@tucnak> (raw)
In-Reply-To: <DB5PR08MB10484FE2601E338FC2E68208987B0@DB5PR08MB1048.eurprd08.prod.outlook.com>
On Tue, Sep 26, 2017 at 12:44:10PM +0000, Sudi Das wrote:
>
> Still waiting on Jakub's comment on whether there are more things needed
> at the backend. But I have updated the patch according to Richard's
> comments.
Well, we don't want to regress performance wise on one of the most important
primary targets. I don't care that much if the RTL/backend work is done
together with the patch, or as a follow-up during stage1/3, but it should be
done, the testcases I've posted can be used as a basis of a P1 runtime
performance regression.
Jakub
next prev parent reply other threads:[~2017-09-26 13:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 11:16 Wilco Dijkstra
2017-04-13 11:21 ` Jakub Jelinek
2017-04-13 11:33 ` Wilco Dijkstra
2017-04-13 11:41 ` Jakub Jelinek
2017-04-13 11:49 ` Richard Biener
2017-04-13 11:55 ` Jakub Jelinek
2017-04-13 12:01 ` Wilco Dijkstra
2017-08-01 9:15 ` Sudi Das
2017-08-04 10:16 ` Richard Biener
2017-09-26 12:44 ` Sudi Das
2017-09-26 13:06 ` Jakub Jelinek [this message]
2017-09-26 13:20 ` Wilco Dijkstra
2017-10-06 17:00 ` Sudi Das
2017-10-09 12:05 ` Richard Biener
2017-10-09 13:04 ` Wilco Dijkstra
2017-10-10 11:12 ` Sudi Das
2017-11-07 12:37 ` Wilco Dijkstra
2017-11-07 14:48 ` Christophe Lyon
2017-11-07 14:49 ` Wilco Dijkstra
-- strict thread matches above, loose matches on Subject: below --
2017-04-12 9:30 Sudi Das
2017-04-12 17:06 ` Jakub Jelinek
2017-04-12 18:16 ` Segher Boessenkool
2017-04-12 18:59 ` Jakub Jelinek
2017-04-12 19:34 ` Segher Boessenkool
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=20170926130612.GR1701@tucnak \
--to=jakub@redhat.com \
--cc=James.Greenhalgh@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Sudi.Das@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--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).