public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/99225] New: ICE in wide_int_to_tree_1, at tree.c:1644 Date: Tue, 23 Feb 2021 18:29:16 +0000 [thread overview] Message-ID: <bug-99225-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99225 Bug ID: 99225 Summary: ICE in wide_int_to_tree_1, at tree.c:1644 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Affects versions down to at least r5 : $ cat z1.c #define vector __attribute__((vector_size(16))) int f () { vector int a = {0, 0, 0, 0}; vector int b = {1, 0, 0, 0}; return (a & (1 << b)) != 0; } $ gcc-11-20210221 -c z1.c z1.c: In function 'f': z1.c:6:3: internal compiler error: in wide_int_to_tree_1, at tree.c:1644 6 | return (a & (1 << b)) != 0; | ^~~~~~ 0xde3e1e wide_int_to_tree_1 ../../gcc/tree.c:1644 0xde433b wide_int_to_tree(tree_node*, poly_int<1u, generic_wide_int<wide_int_ref_storage<false, true> > > const&) ../../gcc/tree.c:1756 0xde433b build_int_cst(tree_node*, poly_int<1u, long>) ../../gcc/tree.c:1396 0x8945ea fold_binary_loc(unsigned int, tree_code, tree_node*, tree_node*, tree_node*) ../../gcc/fold-const.c:12048 0x894caa fold_build2_loc(unsigned int, tree_code, tree_node*, tree_node*, tree_node*) ../../gcc/fold-const.c:13715 0x69e80b c_fully_fold_internal ../../gcc/c/c-fold.c:371 0x69e00d c_fully_fold_internal ../../gcc/c/c-fold.c:623 0x69f0a9 c_fully_fold(tree_node*, bool, bool*, bool) ../../gcc/c/c-fold.c:125 0x65c2cd c_finish_return(unsigned int, tree_node*, tree_node*) ../../gcc/c/c-typeck.c:10742 0x6918b6 c_parser_statement_after_labels ../../gcc/c/c-parser.c:6162 0x69339a c_parser_compound_statement_nostart ../../gcc/c/c-parser.c:5788 0x693c13 c_parser_compound_statement ../../gcc/c/c-parser.c:5597 0x6954c8 c_parser_declaration_or_fndef ../../gcc/c/c-parser.c:2539 0x69c337 c_parser_external_declaration ../../gcc/c/c-parser.c:1777 0x69ce59 c_parser_translation_unit ../../gcc/c/c-parser.c:1650 0x69ce59 c_parse_file() ../../gcc/c/c-parser.c:21984 0x6eccc2 c_common_parse_file() ../../gcc/c-family/c-opts.c:1218
next reply other threads:[~2021-02-23 18:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-23 18:29 gscfq@t-online.de [this message] 2021-02-23 18:46 ` [Bug c/99225] [8/9/10/11 Regression] " jakub at gcc dot gnu.org 2021-02-23 18:52 ` jakub at gcc dot gnu.org 2021-02-23 19:16 ` jakub at gcc dot gnu.org 2021-02-24 11:11 ` [Bug tree-optimization/99225] " cvs-commit at gcc dot gnu.org 2021-02-24 11:15 ` [Bug tree-optimization/99225] [8/9/10 " jakub at gcc dot gnu.org 2021-03-19 23:29 ` cvs-commit at gcc dot gnu.org 2021-03-20 8:08 ` [Bug tree-optimization/99225] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:32 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:51 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` 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-99225-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).