public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/55190] [SH] ivopts causes loop setup bloat Date: Sat, 04 Apr 2015 11:46:00 -0000 [thread overview] Message-ID: <bug-55190-4-0i6aCnw5E4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55190-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55190 --- Comment #6 from Oleg Endo <olegendo at gcc dot gnu.org> --- Another example: const char* test (const char* s0, int c, int* rout) { int r = 0; for (int i = 0; i < c; ++i) // r += s0[i]; r += *s0++; *rout = r; return s0; } On SH compiles to: _test: cmp/pl r5 bf .L4 mov r4,r3 // r3 = s0 add r5,r4 // r4 = s0 + c mov r4,r1 // r1 = s0 + c mov #0,r2 sub r3,r1 // r1 = (s0 + c) - s0 = c (d'uh) .align 2 .L3: mov.b @r3+,r7 dt r1 bf/s .L3 add r7,r2 .L2: mov.l r2,@r6 rts mov r4,r0 .align 1 .L4: bra .L2 mov #0,r2
next prev parent reply other threads:[~2015-04-04 11:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-03 12:16 [Bug target/55190] New: " olegendo at gcc dot gnu.org 2013-02-16 11:13 ` [Bug target/55190] " olegendo at gcc dot gnu.org 2013-06-17 0:13 ` [Bug rtl-optimization/55190] " olegendo at gcc dot gnu.org 2013-09-30 7:16 ` amker.cheng at gmail dot com 2013-10-03 10:00 ` olegendo at gcc dot gnu.org 2014-07-31 18:03 ` olegendo at gcc dot gnu.org 2015-04-04 11:46 ` olegendo at gcc dot gnu.org [this message] 2015-04-07 7:27 ` [Bug rtl-optimization/55190] " olegendo at gcc dot gnu.org 2021-05-04 12:31 ` rguenth at gcc dot gnu.org 2023-07-07 6:49 ` 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-55190-4-0i6aCnw5E4@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).