public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/41868] cell microcode instruction (addic.) is generated for a trivial loop with -O2 optimizations, hurting performance badly Date: Mon, 02 Nov 2009 17:09:00 -0000 [thread overview] Message-ID: <20091102170854.11224.qmail@sourceware.org> (raw) In-Reply-To: <bug-41868-14457@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from pinskia at gcc dot gnu dot org 2009-11-02 17:08 ------- In fact doing the following diff to the -Os assembly: --- t5.Os.s 2009-11-02 23:18:52.000000000 +0900 +++ t5.Os.dot.s 2009-11-02 23:20:19.000000000 +0900 @@ -29,9 +29,9 @@ x: .L4: bl y .L3: - cmpwi 7,31,0 - addi 31,31,-1 - bne 7,.L4 +# cmpwi 7,31,0 + addic. 31,31,-1 + bne .L4 addi 11,1,16 b _restgpr_31_x .size x,.-x produces the same result as -Os on the trunk. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41868
next prev parent reply other threads:[~2009-11-02 17:09 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-29 15:16 [Bug target/41868] New: cell microcode instruction " siarhei dot siamashka at gmail dot com 2009-10-29 15:21 ` [Bug target/41868] cell microcode instruction (addic.) " siarhei dot siamashka at gmail dot com 2009-11-02 16:51 ` pinskia at gcc dot gnu dot org 2009-11-02 16:56 ` pinskia at gcc dot gnu dot org 2009-11-02 17:05 ` pinskia at gcc dot gnu dot org 2009-11-02 17:09 ` pinskia at gcc dot gnu dot org [this message] 2009-11-02 17:10 ` pinskia at gcc dot gnu dot org 2009-11-03 20:09 ` siarhei dot siamashka at gmail dot com [not found] <bug-41868-4@http.gcc.gnu.org/bugzilla/> 2011-11-29 23:21 ` pinskia at gcc dot gnu.org 2011-11-29 23:28 ` pinskia 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=20091102170854.11224.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).