public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46172] New: ICE: in expand_widen_pattern_expr, at optabs.c:522 with -ftree-vectorize -fno-tree-dce Date: Mon, 25 Oct 2010 21:17:00 -0000 [thread overview] Message-ID: <bug-46172-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46172 Summary: ICE: in expand_widen_pattern_expr, at optabs.c:522 with -ftree-vectorize -fno-tree-dce Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Created attachment 22152 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22152 reduced testcase Output - 4.6 (trunk): $ gcc -ftree-vectorize -O -fno-tree-dce pr46172.c pr46172.c: In function 'foo': pr46172.c:3:5: internal compiler error: in expand_widen_pattern_expr, at optabs.c:522 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Output - 4.5: $ gcc -ftree-vectorize -O -fno-tree-dce pr46172.c pr46172.c: In function 'foo': pr46172.c:3:5: internal compiler error: in expand_expr_real_2, at expr.c:8275 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Output - 4.4: $ gcc -ftree-vectorize -O -fno-tree-dce pr46172.c pr46172.c: In function 'foo': pr46172.c:3: internal compiler error: in c_expand_expr, at c-common.c:5015 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r165915 - crash 4.5 r165781 - crash 4.4 r165781 - crash 4.4 r149995 - crash
next reply other threads:[~2010-10-25 21:17 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-25 21:17 zsojka at seznam dot cz [this message] 2010-10-26 7:12 ` [Bug tree-optimization/46172] [4.2/4.3/4.4/4.5/4.6 Regression] " hjl.tools at gmail dot com 2010-10-26 8:21 ` hjl.tools at gmail dot com 2010-10-26 14:01 ` [Bug tree-optimization/46172] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu.org 2010-11-02 9:47 ` jakub at gcc dot gnu.org 2010-11-02 12:39 ` jakub at gcc dot gnu.org 2010-11-02 13:12 ` irar at il dot ibm.com 2010-11-02 13:19 ` jakub at gcc dot gnu.org 2010-11-02 13:28 ` irar at il dot ibm.com 2010-11-02 15:21 ` jakub at gcc dot gnu.org 2010-11-03 11:19 ` jakub at gcc dot gnu.org 2010-11-12 14:46 ` rguenth at gcc dot gnu.org 2010-11-18 15:18 ` rguenth at gcc dot gnu.org 2010-11-18 15:27 ` 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-46172-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).