public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tjw at omnigroup dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/14042] C++ abstraction penalty is high in simple cases Date: Sun, 16 May 2004 23:46:00 -0000 [thread overview] Message-ID: <20040515232351.16715.qmail@sourceware.org> (raw) In-Reply-To: <20040206074537.14042.tjw@omnigroup.com> ------- Additional Comments From tjw at omnigroup dot com 2004-05-15 23:23 ------- This actually looks worse now. Taking the original obj.cpp file and compiling with a fresh checkout of mainline after the merge of tree-ssa, I get the following for iterate_ok: L4: vaddfp v0,v13,v1 addi r9,r1,-96 vmaddfp v13,v0,v13,v1 stvx v0,r9,r0 vsubfp v1,v0,v1 bdnz L4 Note that this used to have no memory operations in the inner loop and now it looks like its repetitively storing the same vector to the stack. Then, for iterate_bad I get: L16: addi r10,r1,-144 vaddfp v1,v9,v10 lvx v0,r10,r0 lvx v13,r10,r2 vaddfp v12,v13,v0 stvx v1,r10,r11 vmaddfp v9,v1,v9,v10 vsubfp v10,v1,v10 vsubfp v11,v12,v0 stvx v12,r10,r9 vmaddfp v13,v12,v13,v0 stvx v11,r10,r0 stvx v13,r10,r2 bdnz L16 This is still chock full of unneeded memory operations. -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14042
next prev parent reply other threads:[~2004-05-15 23:23 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-06 7:45 [Bug c++/14042] New: " tjw at omnigroup dot com 2004-02-06 7:46 ` [Bug c++/14042] " tjw at omnigroup dot com 2004-02-06 7:50 ` [Bug c++/14042] C++ abstraction penalty is high in simple Altivec cases tjw at omnigroup dot com 2004-02-06 7:53 ` tjw at omnigroup dot com 2004-02-06 8:00 ` [Bug optimization/14042] C++ abstraction penalty is high in simple cases pinskia at gcc dot gnu dot org 2004-02-06 15:05 ` segher at kernel dot crashing dot org 2004-02-06 16:57 ` tjw at omnigroup dot com 2004-02-09 10:52 ` segher at kernel dot crashing dot org 2004-02-09 19:08 ` pinskia at gcc dot gnu dot org 2004-02-20 2:54 ` dberlin at gcc dot gnu dot org 2004-02-20 2:56 ` dberlin at gcc dot gnu dot org 2004-03-03 5:52 ` pinskia at gcc dot gnu dot org 2004-03-06 4:00 ` tjw at omnigroup dot com 2004-03-06 4:08 ` pinskia at gcc dot gnu dot org 2004-05-13 20:25 ` [Bug tree-optimization/14042] " pinskia at gcc dot gnu dot org 2004-05-16 23:46 ` tjw at omnigroup dot com [this message] 2004-05-16 23:59 ` pinskia at gcc dot gnu dot org 2004-05-17 13:30 ` pinskia at gcc dot gnu dot org 2004-05-27 8:02 ` pinskia at gcc dot gnu dot org 2004-06-02 4:41 ` pinskia at gcc dot gnu dot org 2004-06-02 18:57 ` pinskia at gcc dot gnu dot org 2004-06-02 18:57 ` cvs-commit at gcc dot gnu dot 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=20040515232351.16715.qmail@sourceware.org \ --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).