public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48740] Raw C++0x strings and trigraphs mix badly
Date: Sat, 23 Apr 2011 10:22:00 -0000 [thread overview]
Message-ID: <bug-48740-4-agMf3rmhR2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48740-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48740
Daniel Krügler <daniel.kruegler at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.kruegler at
| |googlemail dot com
--- Comment #2 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2011-04-23 10:22:27 UTC ---
(In reply to comment #1)
> Just to note: I found this bug with 4.5.2 originally. I then used 4.6 only to
> check that it wasn't solved in the mean time.
Please always ensure that the defect still exists in the most recent compiler
version, which is 4.7. I verified that 4.7.0 20110422 (experimental) still
contains this warning.
In regard to your questions: Standard C++0x does still contain trigraphs, so a
conforming compiler has to handle them correctly. But any trigraph
transformations that happened within a raw string shall be reverted afterwards,
es clearly expressed in [lex.pptoken] p. 3 b. 1:
"If the next character begins a sequence of characters that could be the prefix
and initial double quote of a raw string literal, such as R", the next
preprocessing token shall be a raw string literal. Between the initial and
final double quote characters of the raw string, any transformations performed
in phases 1 and 2 (trigraphs, universal-character-names, and line splicing) are
reverted; this reversion shall apply before any d-char, r-char, or delimiting
parenthesis is identified."
The most important aspect is to test that this is not just a warning, but that
trigraph transformations have indeed been performed. I can confirm this to
happen with gcc 4.7 200110409 (4.7.0 20110422 version cannot produce executable
programs), so this is clearly not only a false warning.
next prev parent reply other threads:[~2011-04-23 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 9:16 [Bug c++/48740] New: " kayhayen at gmx dot de
2011-04-23 9:17 ` [Bug c++/48740] " kayhayen at gmx dot de
2011-04-23 10:22 ` daniel.kruegler at googlemail dot com [this message]
2011-04-23 10:30 ` redi at gcc dot gnu.org
2011-04-23 10:55 ` jakub at gcc dot gnu.org
2011-04-23 10:59 ` daniel.kruegler at googlemail dot com
2011-04-23 11:05 ` redi at gcc dot gnu.org
2011-04-23 11:06 ` kayhayen at gmx dot de
2011-04-23 11:14 ` daniel.kruegler at googlemail dot com
2011-04-23 11:25 ` kayhayen at gmx dot de
2011-04-23 11:36 ` redi at gcc dot gnu.org
2011-04-23 11:56 ` jakub at gcc dot gnu.org
2011-04-23 12:34 ` [Bug preprocessor/48740] " jakub at gcc dot gnu.org
2011-04-23 12:34 ` jakub at gcc dot gnu.org
2011-04-23 15:10 ` kayhayen at gmx dot de
2011-04-23 23:32 ` jakub at gcc dot gnu.org
2011-04-23 23:34 ` jakub at gcc dot gnu.org
2011-04-26 10:07 ` jakub at gcc dot gnu.org
2011-04-26 10:40 ` jakub at gcc dot gnu.org
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=bug-48740-4-agMf3rmhR2@http.gcc.gnu.org/bugzilla/ \
--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).