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++/64959] SFINAE in UDLs
Date: Thu, 12 Feb 2015 20:22:00 -0000	[thread overview]
Message-ID: <bug-64959-4-XtzNgVNoPJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64959-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64959

--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Thu Feb 12 20:21:34 2015
New Revision: 220656

URL: https://gcc.gnu.org/viewcvs?rev=220656&root=gcc&view=rev
Log:
    PR c++/64959
    * parser.c (lookup_literal_operator): Return all candidates.
    (cp_parser_userdef_char_literal): Simplify error handling.
    (cp_parser_userdef_numeric_literal):  Pass tf_warning_or_error.
    (cp_parser_userdef_string_literal): Pass tf_warning_or_error.
    Also give higher priority to standard string UDL operator.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-namespace-ambiguous.C
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-namespace-using-directive.C
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-sfinae-neg.C
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-sfinae.C
    trunk/gcc/testsuite/g++.dg/cpp1y/udlit-char-template-sfinae-neg.C
    trunk/gcc/testsuite/g++.dg/cpp1y/udlit-char-template-sfinae.C
   
trunk/gcc/testsuite/g++.dg/cpp1y/udlit-char-template-vs-std-literal-operator.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/parser.c
    trunk/gcc/testsuite/g++.dg/cpp0x/udlit-resolve.C


  parent reply	other threads:[~2015-02-12 20:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 12:48 [Bug c++/64959] New: " d.truby at warwick dot ac.uk
2015-02-08 22:09 ` [Bug c++/64959] " ville.voutilainen at gmail dot com
2015-02-09 15:09 ` andrea.azzarone at canonical dot com
2015-02-12 20:22 ` jason at gcc dot gnu.org [this message]
2015-02-26 11:30 ` paolo.carlini at oracle 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=bug-64959-4-XtzNgVNoPJ@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).