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/97861] New: [11 Regression] ICE in warn_parm_array_mismatch, at c-family/c-warn.c:3378 Date: Mon, 16 Nov 2020 19:02:09 +0000 [thread overview] Message-ID: <bug-97861-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97861 Bug ID: 97861 Summary: [11 Regression] ICE in warn_parm_array_mismatch, at c-family/c-warn.c:3378 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: --- Changed between 20200823 and 20201004 : $ cat z1.c __attribute__((access(read_only, 2))) void f (int, int*); void f (int a) { } $ gcc-11-20201115 -c z1.c z1.c:2:1: internal compiler error: Segmentation fault 2 | void f (int a) { } | ^~~~ 0xb3b52f crash_signal ../../gcc/toplev.c:330 0x6fef74 warn_parm_array_mismatch(unsigned int, tree_node*, tree_node*) ../../gcc/c-family/c-warn.c:3378 0x641a94 start_function(c_declspecs*, c_declarator*, tree_node*) ../../gcc/c/c-decl.c:9589 0x688a86 c_parser_declaration_or_fndef ../../gcc/c/c-parser.c:2444 0x690297 c_parser_external_declaration ../../gcc/c/c-parser.c:1777 0x690db9 c_parser_translation_unit ../../gcc/c/c-parser.c:1650 0x690db9 c_parse_file() ../../gcc/c/c-parser.c:21882 0x6dfb82 c_common_parse_file() ../../gcc/c-family/c-opts.c:1196
next reply other threads:[~2020-11-16 19:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-16 19:02 gscfq@t-online.de [this message] 2020-11-16 19:46 ` [Bug c/97861] " marxin at gcc dot gnu.org 2020-11-17 7:15 ` rguenth at gcc dot gnu.org 2020-11-18 22:47 ` msebor at gcc dot gnu.org 2020-11-20 21:36 ` cvs-commit at gcc dot gnu.org 2020-11-20 21:44 ` msebor 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-97861-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).