public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/23688] Compiler does not warn on selected unknown character escapes
Date: Thu, 01 Sep 2005 23:11:00 -0000 [thread overview]
Message-ID: <20050901231136.6771.qmail@sourceware.org> (raw)
In-Reply-To: <20050901230506.23688.simon_baldwin@yahoo.com>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-01 23:11 -------
Hmm, interesting if I add -pedantic, I get the warnings.
And this is not a regression. A preprocessor person has to comment on why this is.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Component|c++ |preprocessor
Ever Confirmed| |1
Keywords| |diagnostic
Known to fail| |2.95.3 3.2.3 3.4.0 4.0.0
| |4.1.0 3.0.4
Last reconfirmed|0000-00-00 00:00:00 |2005-09-01 23:11:34
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23688
next prev parent reply other threads:[~2005-09-01 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 23:05 [Bug c++/23688] New: " simon_baldwin at yahoo dot com
2005-09-01 23:11 ` pinskia at gcc dot gnu dot org [this message]
2005-09-01 23:16 ` [Bug preprocessor/23688] " pinskia at gcc dot gnu dot org
[not found] <bug-23688-11271@http.gcc.gnu.org/bugzilla/>
2006-08-18 17:51 ` simon_baldwin at yahoo dot com
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=20050901231136.6771.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).