public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55160] [4.8 Regression] Counterproductive loop induction variable optimization Date: Thu, 01 Nov 2012 07:09:00 -0000 [thread overview] Message-ID: <bug-55160-4-sxeoUgEYp9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55160-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55160 Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|sh*-*-* arm*-*-* |sh*-*-* Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #2 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2012-11-01 07:09:25 UTC --- (In reply to comment #0) > Starting with rev 192505 the following > > int test_04 (int* x, int c) > { > int s = 0; > for (int i = 0; i < c; ++i) > s += *--x; > return s; > } > .. > In this case the inner loop code size effectively does not increase, but there > is overhead in setting up the loop. Similar code is also generated on ARM. In order to get the r192504 arm port to generate a doloop_end pattern, I have to enable thubm2 support and modulo scheduling, e.g.: -O2 --std=c99 -mthumb -march=armv7 -fmodulo-sched with these options, r192505 also gets the doloop_end pattern. Therefore, I have removed arm from the target list.
next prev parent reply other threads:[~2012-11-01 7:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-01 1:41 [Bug rtl-optimization/55160] New: " olegendo at gcc dot gnu.org 2012-11-01 6:28 ` [Bug rtl-optimization/55160] " amylaar at gcc dot gnu.org 2012-11-01 7:09 ` amylaar at gcc dot gnu.org [this message] 2012-11-01 21:29 ` [Bug target/55160] " olegendo 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-55160-4-sxeoUgEYp9@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).