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/109409] New: [13 Regression] ICE in check_format_arg, at c-family/c-format.cc:1777 Date: Tue, 04 Apr 2023 16:09:56 +0000 [thread overview] Message-ID: <bug-109409-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109409 Bug ID: 109409 Summary: [13 Regression] ICE in check_format_arg, at c-family/c-format.cc:1777 Product: gcc Version: 13.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 20220821 and 20220828, with -Wall : $ cat z1.c int g (); void f (char *a) { const char c[g()] = "1"; __builtin_sprintf (a, c); } $ gcc-13-20230402 -c z1.c -Wall z1.c: In function 'f': z1.c:4:23: error: variable-sized object may not be initialized except with an empty initializer 4 | const char c[g()] = "1"; | ^~~ z1.c:5:3: internal compiler error: in check_format_arg, at c-family/c-format.cc:1777 5 | __builtin_sprintf (a, c); | ^~~~~~~~~~~~~~~~~ 0x83216a check_format_arg ../../gcc/c-family/c-format.cc:1777 0x82d680 check_format_info ../../gcc/c-family/c-format.cc:1543 0x82d680 check_function_format(tree_node const*, tree_node*, int, tree_node**, vec<unsigned int, va_heap, vl_ptr>*) ../../gcc/c-family/c-format.cc:1198 0x81a3e5 check_function_arguments(unsigned int, tree_node const*, tree_node const*, int, tree_node**, vec<unsigned int, va_heap, vl_ptr>*) ../../gcc/c-family/c-common.cc:6093 0x775e4d build_function_call_vec(unsigned int, vec<unsigned int, va_heap, vl_ptr>, tree_node*, vec<tree_node*, va_gc, vl_embed>*, vec<tree_node*, va_gc, vl_embed>*, tree_node*) ../../gcc/c/c-typeck.cc:3309 0x7a6d01 c_parser_postfix_expression_after_primary ../../gcc/c/c-parser.cc:11239 0x79461d c_parser_postfix_expression ../../gcc/c/c-parser.cc:10846 0x7a17ba c_parser_unary_expression ../../gcc/c/c-parser.cc:8831 0x7a2b1f c_parser_cast_expression ../../gcc/c/c-parser.cc:8672 0x7a2e1b c_parser_binary_expression ../../gcc/c/c-parser.cc:8440 0x7a44eb c_parser_conditional_expression ../../gcc/c/c-parser.cc:8138 0x7a4d74 c_parser_expr_no_commas ../../gcc/c/c-parser.cc:8052 0x7a5022 c_parser_expression ../../gcc/c/c-parser.cc:11379 0x7a57db c_parser_expression_conv ../../gcc/c/c-parser.cc:11419 0x7c01f3 c_parser_statement_after_labels ../../gcc/c/c-parser.cc:6781 0x7c24db c_parser_compound_statement_nostart ../../gcc/c/c-parser.cc:6296 0x7c2d83 c_parser_compound_statement ../../gcc/c/c-parser.cc:6105 0x7c4d7f c_parser_declaration_or_fndef ../../gcc/c/c-parser.cc:2841 0x7cf0af c_parser_external_declaration ../../gcc/c/c-parser.cc:1925 0x7cf9ed c_parser_translation_unit ../../gcc/c/c-parser.cc:1779
next reply other threads:[~2023-04-04 16:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-04 16:09 gscfq@t-online.de [this message] 2023-04-04 16:30 ` [Bug c/109409] " mpolacek at gcc dot gnu.org 2023-04-04 20:45 ` pinskia at gcc dot gnu.org 2023-04-13 11:38 ` [Bug c/109409] [13 Regression] ICE in check_format_arg, at c-family/c-format.cc:1777 since r13-2205-g14cfa01755a66a jakub at gcc dot gnu.org 2023-04-26 6:58 ` [Bug c/109409] [13/14 " rguenth at gcc dot gnu.org 2023-04-27 9:37 ` cvs-commit at gcc dot gnu.org 2023-04-27 9:42 ` cvs-commit at gcc dot gnu.org 2023-04-27 9:43 ` 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-109409-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).