Re: c/6861: Conflicting type name allowed

Re: c/6861: Conflicting type name allowed

[jsm28]

Synopsis: Conflicting type name allowed

State-Changed-From-To: open->closed
State-Changed-By: jsm28
State-Changed-When: Fri Aug 23 13:18:50 2002
State-Changed-Why:
    Fixed on mainline.  Same as c/4319.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6861

RE: c/6861: Conflicting type name allowed

[Steve Cornett]

The following reply was made to PR c/6861; it has been noted by GNATS.

From: "Steve Cornett" <stevec@bullseye.com>
To: "Andrew Pinski" <pinskia@physics.uc.edu>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: RE: c/6861: Conflicting type name allowed
Date: Wed, 29 May 2002 15:16:55 -0700

 Andrew,
 
 Thanks for your reply, however I disagree with your finding.
 
 A warning is too weak, and very much too weak if -pedantic is required to
 get the warning.  This syntax is not just a little bit off, it is completely
 invalid.  Is the type of "a" unsigned char, unsigned short or (signed)
 short?  Any of these seems plausible to me.  The bug is not that you cannot
 get a warning, but rather that a meaningless, erroneous syntax produces no
 error message.
 
 Thanks,
 Steve
 
 -----Original Message-----
 From: Andrew Pinski [mailto:pinskia@physics.uc.edu]
 Sent: Wednesday, May 29, 2002 3:00 PM
 To: stevec@bullseye.com
 Cc: gcc-gnats@gcc.gnu.org
 Subject: Re: c/6861: Conflicting type name allowed
 
 
 you can use `gcc -Wall -pedantic -c testil.c', which warns about it.
 testil.c:2: warning: long, short, signed or unsigned used invalidly for
 `a'
 collect2: ld returned 1 exit status
 
 On Wednesday, May 29, 2002, at 05:54 , stevec@bullseye.com wrote:
 
 > typedef unsigned char T;
 > T short a;
 >> How-To-Repeat:
 > gcc -c bug.c
 
 

Re: c/6861: Conflicting type name allowed

[Andrew Pinski]

The following reply was made to PR c/6861; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: stevec@bullseye.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/6861: Conflicting type name allowed
Date: Wed, 29 May 2002 17:59:36 -0400

 you can use `gcc -Wall -pedantic -c testil.c', which warns about it.
 testil.c:2: warning: long, short, signed or unsigned used invalidly for 
 `a'
 collect2: ld returned 1 exit status
 
 On Wednesday, May 29, 2002, at 05:54 , stevec@bullseye.com wrote:
 
 > typedef unsigned char T;
 > T short a;
 >> How-To-Repeat:
 > gcc -c bug.c
 

c/6861: Conflicting type name allowed

[stevec]

>Number:         6861
>Category:       c
>Synopsis:       Conflicting type name allowed
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 29 14:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Steve Cornett
>Release:        3.1
>Organization:
>Environment:
all
>Description:
Two conflicting types are incorrectly allowed in the same declaration.  The sample code below ought to trigger an error, but is incorrectly accepted.

typedef unsigned char T;
T short a;
>How-To-Repeat:
gcc -c bug.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: