public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: "Fabien Chêne" <fabien.chene@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ C++ 4.6 Patch] allow uninitialized const or reference members with -fpermissive
Date: Wed, 25 May 2011 08:41:00 -0000	[thread overview]
Message-ID: <4DDC5D4A.1070709@redhat.com> (raw)
In-Reply-To: <BANLkTinrYwnNbH75eMA0LVU-hyOGVRXJZQ@mail.gmail.com>

On 05/24/2011 04:40 PM, Fabien Chêne wrote:
> Indeed. I have also added two testcases to check sfinae on 'new T',
> with and without -fpermissive, which leads to a different result.

We don't want to do that; overload resolution should always produce the 
same result.  We can only be permissive in non-SFINAE context.

Jason

  reply	other threads:[~2011-05-25  1:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-22  4:38 Fabien Chêne
2011-05-22 13:37 ` Jason Merrill
2011-05-24 21:43   ` Fabien Chêne
2011-05-25  8:41     ` Jason Merrill [this message]
2011-05-25  8:47       ` Fabien Chêne
2011-05-25 13:53         ` Jason Merrill

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=4DDC5D4A.1070709@redhat.com \
    --to=jason@redhat.com \
    --cc=fabien.chene@gmail.com \
    --cc=gcc-patches@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).