[PATCH] Have 'this'-returning constructors and destructors to take advantage of the new backend 'returned' attribute

[Stephen Lin]

Here's a freshly rebased pair of patches.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: this-return1.patch
Type: application/octet-stream
Size: 16497 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130603/e3834374/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: this-return2.patch
Type: application/octet-stream
Size: 27254 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130603/e3834374/attachment-0001.obj>
-------------- next part --------------

On May 20, 2013, at 2:08 PM, Stephen Lin <swlin at post.harvard.edu> wrote:

> Hi John,
> 
> Do you think this can go in?
> 
> If you have any suggestions for implementation improvements or extra
> tests (either front-end or back-end) let me know; in addition to the
> front-end tests added in this patch the relevant the back-end tests
> are:
> 
> llvm/test/CodeGen/ARM/this-return.ll
> llvm/test/CodeGen/ARM/returned-ext.ll
> llvm/test/CodeGen/X86/this-return-64.ll
> 
> Thanks,
> Stephen
> 
> On Mon, May 6, 2013 at 6:50 AM, Stephen Lin <swlin at post.harvard.edu> wrote:
>>> Enabling a new and not-necessarily-deeply-tested feature/optimization is
>>> actually specifically the sort of thing we try *not* to do right before a
>>> release branch. :)
>> 
>> Oh OK. Well, I just thought it'd be better if the backend and frontend
>> portions of this went out in the same release. If it's not really
>> worth it at this point then I'm OK waiting. Let me know.
>> 
>> -Stephen