public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/103679] New: ICE after error on nested function with VLA as argument
Date: Mon, 13 Dec 2021 04:29:18 +0000	[thread overview]
Message-ID: <bug-103679-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103679

            Bug ID: 103679
           Summary: ICE after error on nested function with VLA as
                    argument
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: error-recovery, ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Take:

void fn1 ()
{
void fnx ()
  int n;
  int a[n];
}

---- CUT ---
We currently have error messages and then some ICEs:
<source>: In function 'fnx':
<source>:7:1: error: expected declaration specifiers before '}' token
    7 | }
      | ^
<source>:6:7: error: declaration for parameter 'a' but no such parameter
    6 |   int a[n];
      |       ^
<source>:5:7: error: declaration for parameter 'n' but no such parameter
    5 |   int n;
      |       ^
<source>:8: error: expected '{' at end of input
<source>: In function 'fn1':
<source>:7:1: error: expected declaration or statement at end of input
    7 | }
      | ^
<source>:2:6: internal compiler error: n from fnx referenced in fn1
    2 | void fn1 ()
      |      ^~~

             reply	other threads:[~2021-12-13  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  4:29 pinskia at gcc dot gnu.org [this message]
2021-12-13  4:29 ` [Bug c/103679] " pinskia at gcc dot gnu.org
2021-12-13  4:34 ` pinskia 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-103679-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: 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).