public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jfoster@cs.berkeley.edu
To: gcc-gnats@gcc.gnu.org
Subject: c/4319: short accepted on typedef'd char
Date: Thu, 13 Sep 2001 13:26:00 -0000	[thread overview]
Message-ID: <20010913202058.2471.qmail@sourceware.cygnus.com> (raw)

>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


             reply	other threads:[~2001-09-13 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 13:26 jfoster [this message]
2001-09-13 14:01 jsm28
2002-08-21 10:06 jsm28

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=20010913202058.2471.qmail@sourceware.cygnus.com \
    --to=jfoster@cs.berkeley.edu \
    --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: 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).