public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/52614] [4.8 Regression] Test failures in gcc.dg/vect: vectorizing unaligned access Date: Thu, 05 Apr 2012 12:47:00 -0000 [thread overview] Message-ID: <bug-52614-4-Y5GqTEKt6h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52614-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52614 --- Comment #12 from William J. Schmidt <wschmidt at gcc dot gnu.org> 2012-04-05 12:46:12 UTC --- Forget that last comment. As Richard pointed out on gcc-patches: "That's probably more a C language question - you would get valid C rejected with -fno-common. But maybe -ftree-vectorize should suggest -fno-common when it encounters a case it would like to promote alignment for. Not sure if for example Fortran would ever work with -fno-common though."
next prev parent reply other threads:[~2012-04-05 12:47 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-19 10:39 [Bug middle-end/52614] New: " dominiq at lps dot ens.fr 2012-03-19 10:54 ` [Bug testsuite/52614] " rguenth at gcc dot gnu.org 2012-03-19 19:03 ` wschmidt at gcc dot gnu.org 2012-03-20 11:30 ` Greta.Yorsh at arm dot com 2012-03-20 15:22 ` dominiq at lps dot ens.fr 2012-03-20 16:08 ` Greta.Yorsh at arm dot com 2012-03-20 16:50 ` ro at gcc dot gnu.org 2012-03-20 17:27 ` pthaugen at gcc dot gnu.org 2012-03-21 13:01 ` dominiq at lps dot ens.fr 2012-03-21 19:40 ` wschmidt at gcc dot gnu.org 2012-03-28 16:49 ` wschmidt at gcc dot gnu.org 2012-04-05 12:14 ` wschmidt at gcc dot gnu.org 2012-04-05 12:18 ` wschmidt at gcc dot gnu.org 2012-04-05 12:47 ` wschmidt at gcc dot gnu.org [this message] 2012-04-06 14:11 ` dominiq at lps dot ens.fr
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-52614-4-Y5GqTEKt6h@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).