public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94346] [9/10 Regression] ICE due to handle_copy_attribute since r9-3982 Date: Thu, 26 Mar 2020 20:13:51 +0000 [thread overview] Message-ID: <bug-94346-4-AO8dx5y2WZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94346-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94346 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code --- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> --- diag_attr_exclusions() expects either a DECL or a TYPE but here it gets an expression: $ gcc -S pr94346.c pr94346.c:8:33: internal compiler error: tree check: expected class ‘type’, have ‘expression’ (compound_expr) in diag_attr_exclusions, at attribs.c:396 8 | ATTR (copy ((bar (), ((struct A *)(0))[0]))) int m; | ^ pr94346.c:1:35: note: in definition of macro ‘ATTR’ 1 | #define ATTR(...) __attribute__ ((__VA_ARGS__)) | ^~~~~~~~~~~ 0x16c3530 tree_class_check_failed(tree_node const*, tree_code_class, char const*, int, char const*) /src/gcc/trunk/gcc/tree.c:9745 0x8c8271 tree_class_check(tree_node*, tree_code_class, char const*, int, char const*) /src/gcc/trunk/gcc/tree.h:3401 0x8c1c5c diag_attr_exclusions /src/gcc/trunk/gcc/attribs.c:396 0x8c1b67 diag_attr_exclusions /src/gcc/trunk/gcc/attribs.c:379 0x8c2b75 decl_attributes(tree_node**, tree_node*, int, tree_node*) /src/gcc/trunk/gcc/attribs.c:694 0xa45e02 handle_copy_attribute /src/gcc/trunk/gcc/c-family/c-attribs.c:2628 0x8c2c55 decl_attributes(tree_node**, tree_node*, int, tree_node*) /src/gcc/trunk/gcc/attribs.c:713 0x95422d c_parser_struct_declaration /src/gcc/trunk/gcc/c/c-parser.c:3620 0x953a6b c_parser_struct_or_union_specifier /src/gcc/trunk/gcc/c/c-parser.c:3413 0x9528fb c_parser_declspecs(c_parser*, c_declspecs*, bool, bool, bool, bool, bool, bool, bool, c_lookahead_kind) /src/gcc/trunk/gcc/c/c-parser.c:2962 0x95031f c_parser_declaration_or_fndef /src/gcc/trunk/gcc/c/c-parser.c:1960 0x94fe3c c_parser_external_declaration /src/gcc/trunk/gcc/c/c-parser.c:1745 0x94f95d c_parser_translation_unit /src/gcc/trunk/gcc/c/c-parser.c:1618 0x98da25 c_parse_file() /src/gcc/trunk/gcc/c/c-parser.c:21718 0xa19299 c_common_parse_file() /src/gcc/trunk/gcc/c-family/c-opts.c:1186 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2020-03-26 20:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-26 19:02 [Bug c++/94346] New: " jakub at gcc dot gnu.org 2020-03-26 19:03 ` [Bug c++/94346] " jakub at gcc dot gnu.org 2020-03-26 20:13 ` msebor at gcc dot gnu.org [this message] 2020-03-26 20:17 ` msebor at gcc dot gnu.org 2020-03-26 20:25 ` jakub at gcc dot gnu.org 2020-03-27 1:56 ` msebor at gcc dot gnu.org 2020-03-27 20:35 ` cvs-commit at gcc dot gnu.org 2020-03-27 20:42 ` [Bug c++/94346] [9 " msebor at gcc dot gnu.org 2021-06-01 8:17 ` rguenth at gcc dot gnu.org 2022-03-17 19:54 ` msebor at gcc dot gnu.org 2022-05-27 8:49 ` 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-94346-4-AO8dx5y2WZ@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).