On Thu, May 17, 2018 at 1:42 PM Marc Glisse wrote:
> On Thu, 17 May 2018, Richard Biener wrote:
> > On Thu, May 17, 2018 at 1:14 PM Marc Glisse
wrote:
> >
> >> On Thu, 17 May 2018, Jonathan Wakely wrote:
> >
> >>> On 17/05/18 12:54 +0200, Marc Glisse wrote:
> On Mon, 14 May 2018, Jonathan
On Thu, 17 May 2018, Richard Biener wrote:
On Thu, May 17, 2018 at 1:14 PM Marc Glisse wrote:
On Thu, 17 May 2018, Jonathan Wakely wrote:
On 17/05/18 12:54 +0200, Marc Glisse wrote:
On Mon, 14 May 2018, Jonathan Wakely wrote:
As discussed at https://gcc.gnu.org/ml/libstdc++/2018-01/msg0
On Thu, May 17, 2018 at 1:14 PM Marc Glisse wrote:
> On Thu, 17 May 2018, Jonathan Wakely wrote:
> > On 17/05/18 12:54 +0200, Marc Glisse wrote:
> >> On Mon, 14 May 2018, Jonathan Wakely wrote:
> >>
> >>> As discussed at https://gcc.gnu.org/ml/libstdc++/2018-01/msg00073.html
> >>> we can simplif
On Thu, 17 May 2018, Jonathan Wakely wrote:
On 17/05/18 12:54 +0200, Marc Glisse wrote:
On Mon, 14 May 2018, Jonathan Wakely wrote:
As discussed at https://gcc.gnu.org/ml/libstdc++/2018-01/msg00073.html
we can simplify the allocator function for valarray memory. I also
noticed that the _Array
On 17/05/18 12:54 +0200, Marc Glisse wrote:
On Mon, 14 May 2018, Jonathan Wakely wrote:
As discussed at https://gcc.gnu.org/ml/libstdc++/2018-01/msg00073.html
we can simplify the allocator function for valarray memory. I also
noticed that the _Array(size_t) constructor is never used.
*
On Mon, 14 May 2018, Jonathan Wakely wrote:
As discussed at https://gcc.gnu.org/ml/libstdc++/2018-01/msg00073.html
we can simplify the allocator function for valarray memory. I also
noticed that the _Array(size_t) constructor is never used.
* include/bits/valarray_array.h (__valarray_ge
As discussed at https://gcc.gnu.org/ml/libstdc++/2018-01/msg00073.html
we can simplify the allocator function for valarray memory. I also
noticed that the _Array(size_t) constructor is never used.
* include/bits/valarray_array.h (__valarray_get_memory): Remove.
(__valarray_get_sto