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/104532] New: ICE in lvalue_p, at c/c-typeck.cc:4987 Date: Mon, 14 Feb 2022 19:53:20 +0000 [thread overview] Message-ID: <bug-104532-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104532 Bug ID: 104532 Summary: ICE in lvalue_p, at c/c-typeck.cc:4987 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20211205 and 20211212 : $ cat z1.c void f (int x) { #pragma omp target enter data map (to: x->vectors) } $ cat z2.c void f (int x) { #pragma omp target enter data map (to: x->vectors[]) } $ gcc-12-20220213 -c z1.c -fopenmp z1.c: In function 'f': z1.c:3:11: internal compiler error: Segmentation fault 3 | #pragma omp target enter data map (to: x->vectors) | ^~~ 0xc1c3cf crash_signal ../../gcc/toplev.cc:322 0x6c1a46 lvalue_p(tree_node const*) ../../gcc/c/c-typeck.cc:4987 0x6ca5a8 build_component_ref(unsigned int, tree_node*, tree_node*, unsigned int) ../../gcc/c/c-typeck.cc:2470 0x6f742e c_parser_omp_variable_list ../../gcc/c/c-parser.cc:13161 0x6f81dc c_parser_omp_clause_map ../../gcc/c/c-parser.cc:16260 0x700262 c_parser_omp_all_clauses ../../gcc/c/c-parser.cc:17057 0x70d6ae c_parser_omp_target_enter_data ../../gcc/c/c-parser.cc:20904 0x70d6ae c_parser_omp_target ../../gcc/c/c-parser.cc:21195 0x6e7a44 c_parser_pragma ../../gcc/c/c-parser.cc:12499 0x7054a6 c_parser_compound_statement_nostart ../../gcc/c/c-parser.cc:5767 0x705873 c_parser_compound_statement ../../gcc/c/c-parser.cc:5609 0x707128 c_parser_declaration_or_fndef ../../gcc/c/c-parser.cc:2544 0x70e85f c_parser_external_declaration ../../gcc/c/c-parser.cc:1779 0x70f18b c_parser_translation_unit ../../gcc/c/c-parser.cc:1652 0x70f18b c_parse_file() ../../gcc/c/c-parser.cc:23348 0x760792 c_common_parse_file() ../../gcc/c-family/c-opts.cc:1238
next reply other threads:[~2022-02-14 19:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-14 19:53 gscfq@t-online.de [this message] 2022-02-15 17:01 ` [Bug c/104532] " jakub at gcc dot gnu.org 2022-02-16 13:34 ` jakub at gcc dot gnu.org 2022-02-17 9:31 ` cvs-commit at gcc dot gnu.org 2022-02-17 9:35 ` 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-104532-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).