Re: c/4319: short accepted on typedef'd char

Re: c/4319: short accepted on typedef'd char

[jsm28]

Synopsis: short accepted on typedef'd char

State-Changed-From-To: analyzed->closed
State-Changed-By: jsm28
State-Changed-When: Wed Aug 21 09:42:52 2002
State-Changed-Why:
    Fixed for 3.3.

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

Re: c/4319: short accepted on typedef'd char

[jsm28]

Synopsis: short accepted on typedef'd char

Responsible-Changed-From-To: unassigned->jsm28
Responsible-Changed-By: jsm28
Responsible-Changed-When: Thu Sep 13 14:01:57 2001
Responsible-Changed-Why:
    Claiming responsibility for this bug.  The fix is trivial,
    but doing it properly does involve writing a collection
    of testcases for all the valid and invalid uses of type
    specifiers.
State-Changed-From-To: open->analyzed
State-Changed-By: jsm28
State-Changed-When: Thu Sep 13 14:01:57 2001
State-Changed-Why:
    Confirmed as a bug in current 3.1 CVS.  This case will
    give a warning with -pedantic; there are a lot of cases
    where warnings conditional on -pedantic ought to be
    unconditional warnings or errors, and since this is a case
    of nonsense code it ought to be an unconditional error.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4319&database=gcc

c/4319: short accepted on typedef'd char

[jfoster]

>Number:         4319
>Category:       c
>Synopsis:       short accepted on typedef'd char
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 13 13:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Jeff Foster
>Release:        gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)
>Organization:
>Environment:
redhat 7.1, x86
>Description:
gcc allows ``short'' to appear with a typedef'd char:

typedef unsigned char __u8;
__u8 short slot_tablelen;

is accepted, but

unsigned char short slot_tablelen;

is not, which doesn't make sense to me.  (In C99, short is
not allowed with any typedef'd name -- I'm not sure why it's
allowed in gcc.)
>How-To-Repeat:
gcc bad.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="bad.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bad.c"

dHlwZWRlZiB1bnNpZ25lZCBjaGFyIF9fdTg7Cl9fdTggc2hvcnQgc2xvdF90YWJsZWxlbjsK