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/21342] New: [4.0/4.1 Regression] some incompatible external declarations not diagnosed
Date: Mon, 02 May 2005 19:55:00 -0000	[thread overview]
Message-ID: <20050502195533.21342.jsm28@gcc.gnu.org> (raw)

My fix to bug 13801 caused some cases of incompatible declarations with external
linkage (in different scopes) not to be diagnosed.  pushdecl fails to update the
type in the external scope with the new information from the new declaration if
there was already a declaration in the current scope, or to check for
consistency with the type in the external scope in those circumstances.

Test 1:

int f(int (*)[]);
int g() { int f(int (*)[2]); }
int f(int (*)[3]);

Test 2:

extern int a[];
void f(void) { extern int a[]; extern int a[10]; }
extern int a[5];

Test 3:

extern int a[];
void f(void) { extern int a[10]; }
extern int a[5];

-- 
           Summary: [4.0/4.1 Regression] some incompatible external
                    declarations not diagnosed
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned 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=21342


             reply	other threads:[~2005-05-02 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 19:55 jsm28 at gcc dot gnu dot org [this message]
2005-05-02 20:00 ` [Bug c/21342] " pinskia at gcc dot gnu dot org
2005-05-10 12:38 ` cvs-commit at gcc dot gnu dot org
2005-05-10 12:41 ` cvs-commit at gcc dot gnu dot org
2005-05-10 16:41 ` pinskia at gcc dot gnu dot org
2005-05-11 10:18 ` schwab at suse dot de
2005-05-11 10:50 ` 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=20050502195533.21342.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: 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).