public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/109409] [13/14 Regression] ICE in check_format_arg, at c-family/c-format.cc:1777 since r13-2205-g14cfa01755a66a
Date: Thu, 27 Apr 2023 09:37:26 +0000 [thread overview]
Message-ID: <bug-109409-4-BxKw9QhReJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109409-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109409
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:d8842271ebf9a81128df9ae80e1d3b688749eac8
commit r14-288-gd8842271ebf9a81128df9ae80e1d3b688749eac8
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Apr 27 11:36:54 2023 +0200
c: Fix up error-recovery on non-empty VLA initializers [PR109409]
On the following testcase we ICE, because after we emit the
variable-sized object may not be initialized except with an empty
initializer
error we don't really reset the initializer to error_mark_node and then at
-Wformat checking time we ICE on seeing STRING_CST initializer for a VLA.
The following patch just arranges for error_mark_node to be returned after
the error diagnostics.
2023-04-27 Jakub Jelinek <jakub@redhat.com>
PR c/109409
* c-parser.cc (c_parser_initializer): Move diagnostics about
initialization of variable sized object with non-empty initializer
after c_parser_expr_no_commas call and ret.set_error (); after it.
* gcc.dg/pr109409.c: New test.
next prev parent reply other threads:[~2023-04-27 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 16:09 [Bug c/109409] New: [13 Regression] ICE in check_format_arg, at c-family/c-format.cc:1777 gscfq@t-online.de
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 [this message]
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-BxKw9QhReJ@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: link
Be 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).