public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49849] loop optimization prevents vectorization Date: Tue, 26 Jul 2011 09:38:00 -0000 [thread overview] Message-ID: <bug-49849-4-nCoyol8rOh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49849-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49849 --- Comment #3 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2011-07-26 09:38:13 UTC --- Thanks Richard, --param max-completely-peel-times=1 does the trick and, in my real life example, does not have any adverse effect elsewhere while it speeds up the loop as expected. More in general, Do you think that GCC will ever be able to transform things like foo into bar by itself?
next prev parent reply other threads:[~2011-07-26 9:38 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-26 7:46 [Bug tree-optimization/49849] New: " vincenzo.innocente at cern dot ch 2011-07-26 8:31 ` [Bug tree-optimization/49849] " vincenzo.innocente at cern dot ch 2011-07-26 9:21 ` rguenth at gcc dot gnu.org 2011-07-26 9:38 ` vincenzo.innocente at cern dot ch [this message] 2011-07-26 9:46 ` rguenth 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-49849-4-nCoyol8rOh@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).