Re: PR libstdc++/83860 avoid dangling references in valarray closure types

2018-05-02 Thread Jonathan Wakely
dn't count it as a regression. OK thanks for the comments. I think this can probably wait for stage 1. I've committed this to trunk now. commit e41006c3d97121574e9a2f61aea8533c33bd6c40 Author: Jonathan Wakely Date: Fri Apr 6 01:30:19 2018 +0100 PR libstdc++/83860 avoid dangling

Re: PR libstdc++/83860 avoid dangling references in valarray closure types

2018-04-06 Thread Jonathan Wakely
On 6 April 2018 at 09:50, Marc Glisse wrote: > On Fri, 6 Apr 2018, Jonathan Wakely wrote: > >> This attempts to solve some of the problems when mixing std::valarray >> operations and 'auto', by storing nested closure objects as values >> instead of references. This means we don't end up with dangli

Re: PR libstdc++/83860 avoid dangling references in valarray closure types

2018-04-06 Thread Marc Glisse
On Fri, 6 Apr 2018, Jonathan Wakely wrote: This attempts to solve some of the problems when mixing std::valarray operations and 'auto', by storing nested closure objects as values instead of references. This means we don't end up with dangling references to temporary closures that have already b

PR libstdc++/83860 avoid dangling references in valarray closure types

2018-04-06 Thread Jonathan Wakely
erics/valarray/83860.cc: New. I'll commit this to trunk only for now, unless anybody sees a problem with the approach, or thinks the layout changes require new mangled names for the closures. commit 1dd9f0f54457eb2c44c6b1125800d94eaac0cb2f Author: Jonathan Wakely Date: Fri Apr 6 01:30