public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64434] [5 Regression] Performance regression after operand canonicalization (r216728).
Date: Wed, 14 Jan 2015 09:45:00 -0000 [thread overview]
Message-ID: <bug-64434-4-NhFi44qkdd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64434-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64434
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 13 Jan 2015, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64434
>
> Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |jakub at gcc dot gnu.org
>
> --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Shouldn't you cache the result of count_num_stmt in some SSA_NAME_VERSION
> indexed vector? Otherwise it can be expensive on pathological testcases.
> And with the caching I'd hope it should be cheap enough that you could do that
> even outside of loops.
Yes, see my patch review
next prev parent reply other threads:[~2015-01-14 9:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 15:15 [Bug tree-optimization/64434] New: " ysrumyan at gmail dot com
2014-12-29 15:17 ` [Bug tree-optimization/64434] " ysrumyan at gmail dot com
2014-12-29 15:47 ` [Bug tree-optimization/64434] [5 Regression] Performance regression after operand cannibalization (r216728) hjl.tools at gmail dot com
2014-12-29 15:48 ` hjl.tools at gmail dot com
2014-12-29 16:17 ` ysrumyan at gmail dot com
2014-12-29 16:18 ` ysrumyan at gmail dot com
2014-12-29 16:20 ` ysrumyan at gmail dot com
2014-12-29 16:25 ` ysrumyan at gmail dot com
2014-12-29 16:36 ` hjl.tools at gmail dot com
2014-12-29 16:56 ` ysrumyan at gmail dot com
2014-12-29 17:01 ` [Bug tree-optimization/64434] [5 Regression] Performance regression after operand canonicalization (r216728) hjl.tools at gmail dot com
2014-12-29 17:08 ` rguenther at suse dot de
2015-01-13 11:23 ` rguenth at gcc dot gnu.org
2015-01-13 16:04 ` jakub at gcc dot gnu.org
2015-01-14 9:45 ` rguenther at suse dot de [this message]
2015-01-15 11:39 ` ienkovich at gcc dot gnu.org
2015-01-15 11:44 ` rguenth at gcc dot gnu.org
2015-01-15 11:44 ` rguenth at gcc dot gnu.org
2015-01-16 14:23 ` ienkovich at gcc dot gnu.org
2015-02-08 9:34 ` pinskia at gcc dot gnu.org
2015-02-09 10:27 ` ysrumyan at gmail dot com
2015-02-09 10:28 ` ysrumyan at gmail dot com
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=bug-64434-4-NhFi44qkdd@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).