public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/50958] [C++0x] raw literal operator provides incorrect string for integer literal '0'
Date: Mon, 21 Nov 2011 19:44:00 -0000	[thread overview]
Message-ID: <bug-50958-4-UCM3bs1M02@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50958-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50958

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> 2011-11-21 19:27:35 UTC ---
Author: jason
Date: Mon Nov 21 19:27:30 2011
New Revision: 181595

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=181595
Log:
    PR c++/50958
gcc/cp/
    * parser.c (lookup_literal_operator): New.
    (cp_parser_userdef_char_literal): Use it.
    (cp_parser_userdef_numeric_literal): Use it.
    (cp_parser_userdef_string_literal): Use lookup_name.
libcpp/
    * expr.c (cpp_userdef_char_remove_type): Fix typo.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-implicit-conv-neg.C
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-raw-length.C
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-resolve.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/parser.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/c-c++-common/dfp/pr33466.c
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-declare-neg.C
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-member-neg.C
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-raw-op-string-neg.C
    trunk/libcpp/ChangeLog
    trunk/libcpp/expr.c


  parent reply	other threads:[~2011-11-21 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  9:16 [Bug c++/50958] New: " daniel.kruegler at googlemail dot com
2011-11-02 14:00 ` [Bug c++/50958] " 3dw4rd at verizon dot net
2011-11-09 10:50 ` daniel.kruegler at googlemail dot com
2011-11-16 16:07 ` 3dw4rd at verizon dot net
2011-11-21 19:44 ` jason at gcc dot gnu.org [this message]
2011-11-21 20:23 ` jason 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-50958-4-UCM3bs1M02@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).