public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/11943] Accepts invalid declaration "int x[2, 3];" in C99 mode Date: Sat, 16 Aug 2003 13:19:00 -0000 [thread overview] Message-ID: <20030816131932.13811.qmail@sources.redhat.com> (raw) In-Reply-To: <20030816082516.11943.falk@debian.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11943 pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2003-08-16 13:19:31 date| | ------- Additional Comments From pinskia at gcc dot gnu dot org 2003-08-16 13:19 ------- I can confirm this on the mainline (20030815). The problem is that in the c-parse.y (really c-parse.in) The array_declarator is defined as follows: array_declarator: '[' maybe_type_quals_attrs expr ']' { $$ = build_array_declarator ($3, $2, 0, 0); } | '[' maybe_type_quals_attrs ']' { $$ = build_array_declarator (NULL_TREE, $2, 0, 0); } | '[' maybe_type_quals_attrs '*' ']' { $$ = build_array_declarator (NULL_TREE, $2, 0, 1); } | '[' STATIC maybe_type_quals_attrs expr ']' { $$ = build_array_declarator ($4, $3, 1, 0); } /* declspecs_nosc_nots is a synonym for type_quals_attrs. */ | '[' declspecs_nosc_nots STATIC expr ']' { $$ = build_array_declarator ($4, $2, 1, 0); } ; which is different from what C99 says.
next prev parent reply other threads:[~2003-08-16 13:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-16 8:25 [Bug c/11943] New: " falk at debian dot org 2003-08-16 9:04 ` [Bug c/11943] " debian-gcc at lists dot debian dot org 2003-08-16 13:19 ` pinskia at gcc dot gnu dot org [this message] 2003-08-23 1:19 ` dhazeghi at yahoo dot com 2003-10-24 15:39 ` cvs-commit at gcc dot gnu dot org 2003-10-24 16:12 ` pinskia at gcc dot gnu dot 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=20030816131932.13811.qmail@sources.redhat.com \ --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).