On Wed, Jun 13, 2018 at 5:05 PM, Jason Merrill wrote:
> On Wed, Jun 13, 2018 at 4:12 PM, Jason Merrill wrote:
>> On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
>>> The fix for 80178 was broken, because I forgot that copy_fn_p is false
>>> for move constructors. As a result, the calling c
On Wed, Jun 13, 2018 at 5:08 PM, Jakub Jelinek wrote:
>
> On Wed, Jun 13, 2018 at 04:12:25PM -0400, Jason Merrill wrote:
> > On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
> > > The fix for 80178 was broken, because I forgot that copy_fn_p is false
> > > for move constructors. As a result
On Wed, Jun 13, 2018 at 04:12:25PM -0400, Jason Merrill wrote:
> On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
> > The fix for 80178 was broken, because I forgot that copy_fn_p is false
> > for move constructors. As a result, the calling convention for a
> > class with a trivial move cons
On Wed, Jun 13, 2018 at 4:12 PM, Jason Merrill wrote:
> On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
>> The fix for 80178 was broken, because I forgot that copy_fn_p is false
>> for move constructors. As a result, the calling convention for a
>> class with a trivial move constructor and
On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill wrote:
> The fix for 80178 was broken, because I forgot that copy_fn_p is false
> for move constructors. As a result, the calling convention for a
> class with a trivial move constructor and deleted copy constructor
> changed inappropriately.
This p
The fix for 80178 was broken, because I forgot that copy_fn_p is false
for move constructors. As a result, the calling convention for a
class with a trivial move constructor and deleted copy constructor
changed inappropriately.
Tested x86_64-pc-linux-gnu, applying to trunk and 8.
commit d6cc7705f
