public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "josh.m.conner at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55213] vectorizer ignores __restrict__ Date: Thu, 29 Nov 2012 22:18:00 -0000 [thread overview] Message-ID: <bug-55213-4-nay2XXmnDP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55213-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55213 --- Comment #4 from Joshua Conner <josh.m.conner at gmail dot com> 2012-11-29 22:17:50 UTC --- I'm also seeing this same issue in libgfortran's matmul_r8.c, where the inner loop has an aliasing check even though all of the pointer dereferences are via restricted pointers. Again, the problem is worse because the aliasing versioning prevents us from doing vector alignment peeling.
next prev parent reply other threads:[~2012-11-29 22:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-05 11:51 [Bug tree-optimization/55213] New: " vincenzo.innocente at cern dot ch 2012-11-05 12:11 ` [Bug tree-optimization/55213] " jakub at gcc dot gnu.org 2012-11-05 13:29 ` vincenzo.innocente at cern dot ch 2012-11-20 18:06 ` josh.m.conner at gmail dot com 2012-11-29 22:18 ` josh.m.conner at gmail dot com [this message] 2012-11-30 7:45 ` Joost.VandeVondele at mat dot ethz.ch
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-55213-4-nay2XXmnDP@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).