This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [C++ PATCH] c++/78495 inherited ctor and inivis-ref parm

From: Nathan Sidwell <nathan at acm dot org>
To: Jason Merrill <jason at redhat dot com>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 20 Jan 2017 11:12:39 -0500
Subject: Re: [C++ PATCH] c++/78495 inherited ctor and inivis-ref parm
Authentication-results: sourceware.org; auth=none
References: <c4cfe14b-34c2-67f6-4954-85cc5e347ba5@acm.org> <CADzB+2=PEeeSOROFrKLsSdBx9ZiGads13j+OMjM7BQPJA5MrYA@mail.gmail.com>

On 01/20/2017 08:45 AM, Jason Merrill wrote:

Hmm, I would guess that if we're going to do this we need to also use
forward_parm in maybe_thunk_body.

Apparently not needed. maybe_thunk_body is called after we'vegenericized the parent ctor. That ctor's parms have been bashed toreference and have DECL_BY_REFERENCE set appropriately. The clone'sparms have also been bashed, but do not have DECL_BY_REFERENCE set.

For POD struct (which remain as struct T) the backend machinery alreadyDTRT.


nathan

--
Nathan Sidwell

Follow-Ups:
- Re: [C++ PATCH] c++/78495 inherited ctor and inivis-ref parm
  - From: Jason Merrill

References:
- [C++ PATCH] c++/78495 inherited ctor and inivis-ref parm
  - From: Nathan Sidwell
- Re: [C++ PATCH] c++/78495 inherited ctor and inivis-ref parm
  - From: Jason Merrill

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]