public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59594] New: wrong code (by tree vectorizer) at -O3 on x86_64-linux-gnu Date: Tue, 24 Dec 2013 17:14:00 -0000 [thread overview] Message-ID: <bug-59594-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59594 Bug ID: 59594 Summary: wrong code (by tree vectorizer) at -O3 on x86_64-linux-gnu Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: su at cs dot ucdavis.edu The current gcc trunk miscompiles the following testcase on x86_64-linux at -O3 in both 32-bit and 64-bit modes. This is a regression from 4.8.x. It looks like a bug in the tree vectorizer as it goes away with -fno-tree-vectorize. $ gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../gcc-trunk/configure --prefix=/usr/local/gcc-trunk --enable-languages=c,c++ --disable-werror --enable-multilib Thread model: posix gcc version 4.9.0 20131224 (experimental) [trunk revision 206194] (GCC) $ $ gcc-trunk -O2 small.c; a.out 0 $ gcc-trunk -O3 -fno-tree-vectorize small.c; a.out 0 $ gcc-trunk -O3 small.c; a.out 1 $ ------------------------------- int printf (const char *, ...); int a; static int b[7]; int main () { for (a = 5; a >= 0; a--) { b[a + 1] = b[a]; b[a] = 1; } printf ("%d\n", b[1]); return 0; }
next reply other threads:[~2013-12-24 17:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-24 17:14 su at cs dot ucdavis.edu [this message] 2013-12-24 18:10 ` [Bug tree-optimization/59594] [4.9 Regression] " hjl.tools at gmail dot com 2013-12-24 18:37 ` hjl.tools at gmail dot com 2014-01-13 10:19 ` jakub at gcc dot gnu.org 2014-01-13 13:47 ` hjl.tools at gmail dot com 2014-01-13 14:02 ` jakub at gcc dot gnu.org 2014-01-22 13:22 ` jakub at gcc dot gnu.org 2014-01-24 10:03 ` jakub at gcc dot gnu.org 2014-01-29 9:28 ` jakub at gcc dot gnu.org 2014-01-29 11:04 ` jakub 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-59594-4@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).