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/48739] New: ICE in check_loop_closed_ssa_use() with "-ftree-parallelize-loops=2 -fno-tree-dominator-opts" Date: Sat, 23 Apr 2011 07:36:00 -0000 [thread overview] Message-ID: <bug-48739-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48739 Summary: ICE in check_loop_closed_ssa_use() with "-ftree-parallelize-loops=2 -fno-tree-dominator-opts" 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 24077 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24077 Output of "ajo-gcc -w -O1 -ftree-parallelize-loops=2 -fno-tree-dominator-opts -c test1942241936.c -v" This reproduces for me with svn revision 172796 (2011-04-20), but it doesn't reproduce with gcc-4.5. I'm on Ubuntu 10.10, x86-64. Attached "gcc-v.txt". cat >test1942241936.c <<EOF extern int g; extern void func_48(void); int func_70(int p) { int a, b, *ptr = &g; for (a = 0; a < 10; ++a) { func_48(); for (b = 0; b < 5; ++b) { for (g = 0; g < 1; ++g) { p = 0; ptr = &p; } } } *ptr = p; for (p = 0; p != 10; p += 3u) { } return g; } EOF gcc -w -O1 -ftree-parallelize-loops=2 -fno-tree-dominator-opts -c test1942241936.c test1942241936.c: In function ‘func_70’: test1942241936.c:3:5: internal compiler error: in check_loop_closed_ssa_use, at tree-ssa-loop-manip.c:422 This test case is reduced from the output of Csmith (http://embed.cs.utah.edu/csmith/), using the following command line: csmith --bitfields --packed-struct -s 1942241936 >test1942241936.c Notice that the final for-loop has undefined behavior due to signed integer overflow, which might be putting the compiler in an unfamiliar state... but surely it shouldn't *crash* the compiler! -fwrapv doesn't make the crash go away, either.
next reply other threads:[~2011-04-23 7:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-23 7:36 arthur.j.odwyer at gmail dot com [this message] 2011-08-19 16:43 ` [Bug tree-optimization/48739] [4.5/4.6/4.7 Regression] " jakub at gcc dot gnu.org 2011-08-19 16:58 ` jakub at gcc dot gnu.org 2011-08-19 18:04 ` jakub at gcc dot gnu.org 2011-08-19 23:05 ` rguenth at gcc dot gnu.org 2011-08-20 7:51 ` jakub at gcc dot gnu.org 2011-08-20 7:58 ` jakub at gcc dot gnu.org 2011-08-20 8:32 ` [Bug tree-optimization/48739] [4.5 " jakub at gcc dot gnu.org 2012-06-20 12:59 ` rguenth at gcc dot gnu.org 2012-07-02 9:51 ` 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-48739-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).