public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: gcc-gnats@gcc.gnu.org Subject: c/9166: [2003-01-03] C front end's type scoping not right Date: Sat, 04 Jan 2003 00:36:00 -0000 [thread overview] Message-ID: <20030104003208.8624.qmail@sources.redhat.com> (raw) >Number: 9166 >Category: c >Synopsis: [2003-01-03] C front end's type scoping not right >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jan 03 16:36:00 PST 2003 >Closed-Date: >Last-Modified: >Originator: neil@gcc.gnu.org >Release: GCC 3.4 and earlier >Organization: >Environment: >Description: /* Compile the code snippet below with -pedantic. The code is illegal because the function f is redeclared with an incompatible prototype, but GCC doesn't winge. */ struct bar {int x, y;}; void foo () { extern void f( struct bar {double x, y;} ); } void f (struct bar ); >How-To-Repeat: >Fix: I doubt it's easy with the current code. Best idea is to clean up the front-end's handling of scopes; it's too messy and obfuscated. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-04 0:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-04 0:36 neil [this message] 2003-01-04 11:26 Joseph S. Myers 2003-01-04 13:36 Neil Booth 2003-01-08 1:03 bangerth 2003-03-01 8:37 neil
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=20030104003208.8624.qmail@sources.redhat.com \ --to=neil@gcc.gnu.org \ --cc=gcc-gnats@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).