public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kayhayen at gmx dot de" <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 11:06:00 -0000 [thread overview] Message-ID: <bug-48740-4-scbQxPhZAc@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 --- Comment #7 from Kay Hayen <kayhayen at gmx dot de> 2011-04-23 11:05:52 UTC --- Created attachment 24079 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24079 Sorry for the typo, that's what you get for extracting test case. This one is better. With this one I can reproduce my original worry indeed: [~]> g++ -c --std=c++0x testcase.cpp -Wall -Werror testcase.cpp:2:17: error: unterminated raw string testcase.cpp:2:15: error: expected primary-expression at end of input testcase.cpp:2:15: error: expected ‘,’ or ‘;’ at end of input Since the trigraph eats up the trigraph terminator, it's not terminated. Now imagine a second constant in the same file and you do get a corrupted output.
next prev parent reply other threads:[~2011-04-23 11:06 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 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 [this message] 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-scbQxPhZAc@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: 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).