public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/53636] SLP may create invalid unaligned memory accesses Date: Fri, 15 Jun 2012 13:30:00 -0000 [thread overview] Message-ID: <bug-53636-4-GkXdsfE3iE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53636-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53636 --- Comment #1 from Ulrich Weigand <uweigand at gcc dot gnu.org> 2012-06-15 13:30:40 UTC --- Author: uweigand Date: Fri Jun 15 13:30:36 2012 New Revision: 188661 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188661 Log: gcc/ PR tree-optimization/53636 * tree-vect-data-refs.c (vect_compute_data_ref_alignment): Verify stride when doing basic-block vectorization. gcc/testsuite/ PR tree-optimization/53636 * gcc.target/arm/pr53636.c: New test. Added: trunk/gcc/testsuite/gcc.target/arm/pr53636.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vect-data-refs.c
next prev parent reply other threads:[~2012-06-15 13:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-11 17:22 [Bug tree-optimization/53636] New: " uweigand at gcc dot gnu.org 2012-06-11 17:24 ` [Bug tree-optimization/53636] " uweigand at gcc dot gnu.org 2012-06-15 13:30 ` uweigand at gcc dot gnu.org [this message] 2012-06-15 15:12 ` uweigand at gcc dot gnu.org 2012-06-26 9:06 ` uweigand at gcc dot gnu.org 2012-09-29 23:56 ` [Bug tree-optimization/53636] [4.7 Regression] " pinskia at gcc dot gnu.org 2012-12-03 15:33 ` rguenth at gcc dot gnu.org 2013-04-11 8:00 ` rguenth at gcc dot gnu.org 2014-06-12 13:12 ` 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-53636-4-GkXdsfE3iE@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).