public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49093] New: ICE in vect_enhance_data_refs_alignment() with volatile inside peeled loop Date: Fri, 20 May 2011 19:08:00 -0000 [thread overview] Message-ID: <bug-49093-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49093 Summary: ICE in vect_enhance_data_refs_alignment() with volatile inside peeled loop Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: arthur.j.odwyer@gmail.com Created attachment 24311 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24311 Output of "ajo-gcc -std=c99 -w -O1 -funswitch-loops -ftree-vectorize -fno-tree-fre test.c -v" This reproduces for me with svn revision 173843 (2011-05-17). It doesn't reproduce with gcc 4.5.1. I'm on Ubuntu 10.10, x86-64. cat >test.c <<EOF volatile unsigned char g_324[4] = {0, 1, 0, 1}; int x, y; void func_81() { int l_466, l_439[7] = {0}; lbl_473: if (x) { for (int g_97 = 0; (g_97 < 4); ++g_97) { if (y) goto lbl_473; g_324[g_97]; l_466 = l_439[g_97]; } foo(l_466); } } EOF gcc -std=c99 -w -O1 -funswitch-loops -ftree-vectorize -fno-tree-fre test.c test.c: In function ‘func_81’: test.c:3:6: internal compiler error: in vect_enhance_data_refs_alignment, at tree-vect-data-refs.c:1551 This test case is reduced from the output of Csmith 2.1.0 (git hash 01aa8b04, https://github.com/Quuxplusone/csmith/), using the following command line: csmith --no-paranoid --no-longlong --no-pointers --arrays --jumps --consts --volatiles --no-checksum --no-divs --no-muls --no-bitfields --packed-struct -s 799267216
next reply other threads:[~2011-05-20 19:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-20 19:08 arthur.j.odwyer at gmail dot com [this message] 2011-05-21 9:54 ` [Bug tree-optimization/49093] [4.6/4.7 Regression] " rguenth at gcc dot gnu.org 2011-05-21 16:53 ` hjl.tools at gmail dot com 2011-05-31 7:42 ` irar at il dot ibm.com 2011-05-31 8:31 ` rguenther at suse dot de 2011-05-31 8:36 ` irar at il dot ibm.com 2011-05-31 8:54 ` rguenther at suse dot de 2011-05-31 9:10 ` irar at il dot ibm.com 2011-05-31 9:18 ` rguenther at suse dot de 2011-05-31 9:24 ` irar at il dot ibm.com 2011-05-31 12:46 ` irar at gcc dot gnu.org 2011-06-02 7:03 ` irar at gcc dot gnu.org 2011-06-02 7:12 ` irar at il dot ibm.com
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-49093-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).