From: Jakub Jelinek <jakub@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>,
Marek Polacek <polacek@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] c: Fix up error-recovery on non-empty VLA initializers [PR109409]
Date: Fri, 14 Apr 2023 21:20:48 +0200 [thread overview]
Message-ID: <ZDmnkLaA8EX5RyFz@tucnak> (raw)
Hi!
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.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2023-04-14 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.
--- gcc/c/c-parser.cc.jj 2023-02-18 12:38:30.759025693 +0100
+++ gcc/c/c-parser.cc 2023-04-13 13:09:13.287373656 +0200
@@ -5677,11 +5677,14 @@ c_parser_initializer (c_parser *parser,
{
struct c_expr ret;
location_t loc = c_parser_peek_token (parser)->location;
- if (decl != error_mark_node && C_DECL_VARIABLE_SIZE (decl))
- error_at (loc,
- "variable-sized object may not be initialized except "
- "with an empty initializer");
ret = c_parser_expr_no_commas (parser, NULL);
+ if (decl != error_mark_node && C_DECL_VARIABLE_SIZE (decl))
+ {
+ error_at (loc,
+ "variable-sized object may not be initialized except "
+ "with an empty initializer");
+ ret.set_error ();
+ }
/* This is handled mostly by gimplify.cc, but we have to deal with
not warning about int x = x; as it is a GCC extension to turn off
this warning but only if warn_init_self is zero. */
--- gcc/testsuite/gcc.dg/pr109409.c.jj 2023-04-13 13:31:52.865765576 +0200
+++ gcc/testsuite/gcc.dg/pr109409.c 2023-04-13 13:13:26.994714440 +0200
@@ -0,0 +1,10 @@
+/* PR c/109409 */
+/* { dg-do compile } */
+/* { dg-options "-Wall" } */
+
+void
+foo (int n)
+{
+ const char c[n] = "1"; /* { dg-error "variable-sized object may not be initialized except with an empty initializer" } */
+ __builtin_printf (c);
+}
Jakub
next reply other threads:[~2023-04-14 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 19:20 Jakub Jelinek [this message]
2023-04-24 20:48 ` Joseph Myers
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=ZDmnkLaA8EX5RyFz@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=polacek@redhat.com \
/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).