public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64434] New: Performance regression after operand canonicalization (r216728). Date: Mon, 29 Dec 2014 15:15:00 -0000 [thread overview] Message-ID: <bug-64434-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64434 Bug ID: 64434 Summary: Performance regression after operand canonicalization (r216728). Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ysrumyan at gmail dot com We noticed huge regression on eembc1.1 and eembc2.0 for 32-bit target at x86. It can be reproduced on attached test-case: before this fix number of %esp references in assembly was 2 but after r216728 - 24. Note that simple fix resolving this issue was sent for review.
next reply other threads:[~2014-12-29 15:15 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-29 15:15 ysrumyan at gmail dot com [this message] 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 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@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: linkBe 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).