From: Jeff Law <law@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>,
Sebastian Pop <sebpop@gmail.com>
Cc: Steve Ellcey <sellcey@mips.com>,
David Malcolm <dmalcolm@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
james.greenhalgh@arm.com, Jakub Jelinek <jakub@redhat.com>
Subject: Re: RFC: Patch for switch elimination (PR 54742)
Date: Fri, 15 Aug 2014 13:26:00 -0000 [thread overview]
Message-ID: <53EE0A74.1080909@redhat.com> (raw)
In-Reply-To: <CAFiYyc2-iXCLy_QOizOHCpq-Ckfkd=T40qind80-07p_fDtaRA@mail.gmail.com>
On 08/15/14 04:07, Richard Biener wrote:
> On Thu, Aug 14, 2014 at 8:45 PM, Sebastian Pop <sebpop@gmail.com> wrote:
>> Steve Ellcey wrote:
>>> I understand the desire not to add optimizations just for benchmarks but
>>> we do know other compilers have added this optimization for coremark
>>> (See
>>> http://community.arm.com/groups/embedded/blog/2013/02/21/coremark-and-compiler-performance)
>>> and the 13 people on the CC list for this bug certainly shows interest in
>>> having it even if it is just for a benchmark. Does 'competing against other
>>> compilers' sound better then 'optimizing for a benchmark'?
>>
>> I definitely would like to see GCC trunk do this transform. What about we
>> integrate the new pass, and then when jump-threading manages to catch the
>> coremark loop, we remove the pass?
>
> It never worked that way.
>
> A new pass takes compile-time, if we disable it by default it won't help
> coremark (and it will bitrot quickly).
>
> So - please fix DOM instead.
Steve's work is highly likely to be faster than further extending the
threading code -- that's one of the primary reasons I suggested Steve
resurrect his work.
Jeff
next prev parent reply other threads:[~2014-08-15 13:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 17:47 Steve Ellcey
2014-08-12 17:56 ` Jakub Jelinek
2014-08-12 18:31 ` Jeff Law
2014-08-12 20:23 ` Richard Biener
2014-08-12 20:40 ` Jeff Law
2014-08-12 22:45 ` Steve Ellcey
2014-08-13 20:55 ` Sebastian Pop
2014-08-13 21:06 ` Jeff Law
2014-08-13 21:33 ` Sebastian Pop
2014-08-14 10:32 ` Richard Biener
2014-08-14 15:56 ` Jeff Law
2014-08-14 16:29 ` David Malcolm
2014-08-14 16:21 ` Jeff Law
2014-08-14 18:25 ` Steve Ellcey
2014-08-14 18:45 ` Sebastian Pop
2014-08-15 10:07 ` Richard Biener
2014-08-15 13:26 ` Jeff Law [this message]
2014-08-15 10:13 ` Richard Biener
2014-08-15 10:44 ` Richard Biener
2014-08-15 15:58 ` Ramana Radhakrishnan
2014-08-13 2:54 ` Bin.Cheng
2014-08-13 9:52 ` Richard Biener
2014-08-14 17:45 ` Steve Ellcey
2014-08-13 9:44 ` Richard Biener
2014-09-03 21:22 ` Jeff Law
2014-09-04 12:57 ` Richard Biener
2014-09-04 13:07 ` Jakub Jelinek
2014-09-04 14:05 ` 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=53EE0A74.1080909@redhat.com \
--to=law@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=james.greenhalgh@arm.com \
--cc=richard.guenther@gmail.com \
--cc=sebpop@gmail.com \
--cc=sellcey@mips.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).