From mboxrd@z Thu Jan 1 00:00:00 1970 From: jsm28@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jfoster@cs.berkeley.edu, jsm28@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c/4319: short accepted on typedef'd char Date: Thu, 13 Sep 2001 14:01:00 -0000 Message-id: <20010913210157.16093.qmail@sourceware.cygnus.com> X-SW-Source: 2001-09/msg00272.html List-Id: 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