This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [v3] Implement resolution of DR 630
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: libstdc++ at gcc dot gnu dot org, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 23 Jul 2009 23:42:56 +0200
- Subject: Re: [v3] Implement resolution of DR 630
- References: <4A670520.6090801@oracle.com> <4A68D57F.7090101@redhat.com>
Hi Jason,
> On 07/22/2009 08:25 AM, Paolo Carlini wrote:
>> -- Jason, while working on this issue, I noticed that:
>>
>> valarray<int> v1;
>> v1 = { };
>>
>> compiles just fine in -std=c++0x mode and, for the assignment, ends up
>> being selected:
>>
>> operator=(const Tp&)
>>
>> with Tp == 0.
> That's odd, I'll take a look. When you say 0, you mean it's a null
> reference?
Thanks. That's imprecise, yes. For the time being I can say for sure
that, inside operator=(const _Tp& __t), this is what gdb prints:
(gdb) p __t
$1 = (const int &) @0x7fffffffdda8: 0
Paolo.