public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <20010913210157.16093.qmail@sourceware.cygnus.com> (raw) 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
next reply other threads:[~2001-09-13 14:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-13 14:01 jsm28 [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-21 10:06 jsm28 2001-09-13 13:26 jfoster
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=20010913210157.16093.qmail@sourceware.cygnus.com \ --to=jsm28@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=jfoster@cs.berkeley.edu \ --cc=nobody@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: linkBe 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).