public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/23143] New: [4.1 Regression] parameter forward declarations broken Date: Fri, 29 Jul 2005 23:30:00 -0000 [thread overview] Message-ID: <20050729232527.23143.jsm28@gcc.gnu.org> (raw) The new C parser lost a call to mark_forward_parm_decls, thereby completely breaking the GNU extension of forward parameter declarations. I'm testing a patch. Testcases: int f1(int a; int a); should be accepted (rather than complaining about a duplicate parameter name), int h1(int a; int b); should be rejected. Observations: 1. This is the first new C parser bug affecting valid code found since the parser went in in February. 2. It suggests that no-one is using this extension. 3. I'm surprised that mark_forward_parm_decls didn't get removed as an unused function after the call was lost. 4. The patch I'm testing restores things to the same functionality as in 4.0. There are various cases of invalid code involving this extension which 3.4 diagnoses and 4.0 doesn't; I'll file a separate bug for those. -- Summary: [4.1 Regression] parameter forward declarations broken Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: jsm28 at gcc dot gnu dot org ReportedBy: jsm28 at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23143
next reply other threads:[~2005-07-29 23:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-29 23:30 jsm28 at gcc dot gnu dot org [this message] 2005-07-29 23:31 ` [Bug c/23143] " pinskia at gcc dot gnu dot org 2005-07-29 23:58 ` joseph at codesourcery dot com 2005-07-30 2:12 ` cvs-commit at gcc dot gnu dot org 2005-07-30 5:33 ` 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=20050729232527.23143.jsm28@gcc.gnu.org \ --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).