public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhongyunde at huawei dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/66084] New: ICE:internal compiler error: in fold_convert_loc, at fold-const.c:1974 Date: Sat, 09 May 2015 07:02:00 -0000 [thread overview] Message-ID: <bug-66084-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66084 Bug ID: 66084 Summary: ICE:internal compiler error: in fold_convert_loc, at fold-const.c:1974 Product: gcc Version: 4.7.4 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: zhongyunde at huawei dot com Target Milestone: --- Created attachment 35509 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35509&action=edit a small case compile with -O2 can reproduce the issue bug issue: crash1.c: In function 'func_32': crash1.c:1128:1: internal compiler error: in fold_convert_loc, at fold-const.c:1974 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. 1972: TREE_TYPE (orig), arg)); 1973: gcc_assert (TREE_CODE (orig) == VECTOR_TYPE 1974: && "tree_int_cst_equal (TYPE_SIZE (type), TYPE_SIZE (orig))"); 1975: return fold_build1_loc (loc, NOP_EXPR, type, arg); testcase: __attribute__ ((vector_size (16))) g_73 = {0x15FE687EL, 0x5827DF98L, 0xF8411272L, 0x235E695dL}; __attribute__ ((vector_size (16))) g_1124; int func_1(void) { __attribute__ ((vector_size (16))) l_1117 = {0x15FE688EL, 0x5827DF98L, 0xF8411272L, 0x235E695EL}; __attribute__ ((vector_size (16))) zhong = ( g_73 <= g_73); g_1124 = (((g_73 < l_1117) == zhong) << 9) ; return 0; }
next reply other threads:[~2015-05-09 7:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-09 7:02 zhongyunde at huawei dot com [this message] 2015-05-09 7:10 ` [Bug c/66084] " zhongyunde at huawei dot com 2015-05-09 7:16 ` pinskia at gcc dot gnu.org 2015-05-09 10:17 ` [Bug middle-end/66084] " glisse at gcc dot gnu.org 2015-05-12 11:53 ` zhongyunde at huawei dot 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-66084-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).