public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "3dw4rd at verizon dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60249] [c++11] Compiler goes into semi-infinite loop with wrong usage of user defined string literals Date: Fri, 27 Jun 2014 21:36:00 -0000 [thread overview] Message-ID: <bug-60249-4-FiBCvDTW8Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60249-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249 --- Comment #4 from Ed Smith-Rowland <3dw4rd at verizon dot net> --- Created attachment 33022 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33022&action=edit Patch 58781, 59867, 60249, ... I think I got it. Don't mess with the token stream. PR C++/58781 - Unicode strings broken in a strange way PR C++/59867 - Template string literal loses first symbol PR C++/60249 - Compiler goes into semi-infinite loop with wrong usage of user defined string literals Plus I fixed an misleading error message for string literal operator templates (not available in C++11).
next prev parent reply other threads:[~2014-06-27 21:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-17 21:18 [Bug c++/60249] New: " reichelt at gcc dot gnu.org 2014-04-17 13:38 ` [Bug c++/60249] " paolo.carlini at oracle dot com 2014-06-25 17:45 ` paolo.carlini at oracle dot com 2014-06-26 14:51 ` 3dw4rd at verizon dot net 2014-06-27 21:36 ` 3dw4rd at verizon dot net [this message] 2014-06-27 21:39 ` paolo.carlini at oracle dot com 2014-06-28 13:28 ` 3dw4rd at verizon dot net 2014-06-28 13:28 ` 3dw4rd at verizon dot net 2014-06-28 14:03 ` paolo.carlini at oracle dot com 2014-06-28 14:21 ` 3dw4rd at verizon dot net 2014-06-28 14:48 ` 3dw4rd at verizon dot net 2014-07-01 3:14 ` emsr at gcc dot gnu.org 2014-07-01 5:31 ` emsr at gcc dot gnu.org 2014-07-01 5:32 ` emsr 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-60249-4-FiBCvDTW8Y@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).