[Bug c/21343] New: [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[Bug c/21343] New: [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[jsm28 at gcc dot gnu dot org]

My fix to bug 13801 caused the compiler no longer to diagnose incompatible
refinements in nested scopes of the types of objects or functions with internal
linkage.  (Fixing this involves adding a special "internal scope", like the
"external scope", which stores the full composite type information for entities
with internal linkage.)  See also bug 21342.

Test 1:

static int (*a)[];
void f(void) { extern int (*a)[2]; }
void g(void) { extern int (*a)[3]; }

Test 2 (where the prototype information from the inner scope should be checked
against the old-style definition):

static int f(int (*)[]);
int g() { extern int f(int (*)[2]); }
static int f(a) int (*a)[3]; { return 0; }

Test 3:

static int (*a)[];
void f(void) { extern int (*a)[]; extern int (*a)[2]; }
extern int (*a)[3];

-- 
           Summary: [4.0/4.1 Regression] incompatible internal linkage
                    declarations in different scopes 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=21343

[Bug c/21343] [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-02 20:02 -------
Confirmed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
           Keywords|                            |accepts-invalid, diagnostic
   Last reconfirmed|0000-00-00 00:00:00         |2005-05-02 20:02:11
               date|                            |
   Target Milestone|---                         |4.0.1


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343

[Bug c/21343] [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[mmitchel at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.0.1                       |4.0.2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343

[Bug c/21343] [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[mmitchel at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.0.2                       |4.0.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343

[Bug c/21343] [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[mmitchel at gcc dot gnu dot org]

------- Comment #4 from mmitchel at gcc dot gnu dot org  2005-10-31 03:14 -------
Downgraded to P5; this will never be release-critical.


-- 

mmitchel at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P5


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343

[Bug c/21343] [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[joseph at codesourcery dot com]

------- Comment #3 from joseph at codesourcery dot com  2005-10-29 20:48 -------
Subject: Re:  [4.0/4.1 Regression] incompatible internal linkage
 declarations in different scopes not diagnosed

On Sat, 29 Oct 2005, pinskia at gcc dot gnu dot org wrote:

> Should this block PR 16620 and PR 16989?

No, because there is no requirement for a diagnostic in these cases; they 
are all compile-time undefined behavior.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343

[Bug c/21343] [4.0/4.1 Regression] incompatible internal linkage declarations in different scopes not diagnosed

[pinskia at gcc dot gnu dot org]

------- Comment #2 from pinskia at gcc dot gnu dot org  2005-10-29 20:45 -------
Should this block PR 16620 and PR 16989?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343