public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52890] Revision 185336 causes 10% degradation on cpu2000 benchmark 252.eon Date: Wed, 12 Sep 2012 23:05:00 -0000 [thread overview] Message-ID: <bug-52890-4-0lrUMjeikI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52890-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52890 --- Comment #10 from Pat Haugen <pthaugen at gcc dot gnu.org> 2012-09-12 23:04:55 UTC --- Created attachment 28181 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28181 Reduced testcase Martin, Have you done any more digging on this? I just discovered that cpu2006 benchmark 471.omnetpp suffers the same problem (8 byte loads turned in to sequence of byte loads/shifts/ors). It causes a 12% degradation on PowerPC, and also goes away when -fno-ipa-sra is added. I'm attaching a reduced testcase that can be compiled with g++ -S -O3 -m64 -mcpu=power7.
next prev parent reply other threads:[~2012-09-12 23:05 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-06 16:59 [Bug middle-end/52890] New: " pthaugen at gcc dot gnu.org 2012-04-06 21:14 ` [Bug middle-end/52890] " pthaugen at gcc dot gnu.org 2012-04-10 12:07 ` rguenth at gcc dot gnu.org 2012-04-10 16:14 ` pthaugen at gcc dot gnu.org 2012-04-10 17:53 ` pthaugen at gcc dot gnu.org 2012-04-11 14:32 ` jamborm at gcc dot gnu.org 2012-04-11 15:54 ` jamborm at gcc dot gnu.org 2012-04-11 16:06 ` jamborm at gcc dot gnu.org 2012-04-11 18:35 ` pthaugen at gcc dot gnu.org 2012-04-17 15:53 ` jamborm at gcc dot gnu.org 2012-09-12 15:24 ` dje at gcc dot gnu.org 2012-09-12 23:05 ` pthaugen at gcc dot gnu.org [this message] 2012-09-14 13:55 ` jamborm at gcc dot gnu.org 2012-11-27 20:48 ` jamborm at gcc dot gnu.org 2012-11-30 16:12 ` jamborm at gcc dot gnu.org 2012-12-03 13:26 ` jamborm at gcc dot gnu.org
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-52890-4-0lrUMjeikI@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).