[v3 PATCH] Make sure the return value of malloc_allocator::allocate is zero-initialized so that checking it for non-zero works later.

Jonathan Wakely jwakely@redhat.com
Sun Oct 16 13:14:00 GMT 2016


On 15/10/16 23:44 +0300, Ville Voutilainen wrote:
>On 15 October 2016 at 22:44, Ville Voutilainen
><ville.voutilainen@gmail.com> wrote:
>> 2016-10-15  Ville Voutilainen  <ville.voutilainen@gmail.com>
>>
>>     Make sure the return value of malloc_allocator::allocate
>>     is zero-initialized so that checking it for non-zero works
>>     later.
>>     * include/ext/malloc_allocator.h (malloc_allocator::allocate):
>>     Initialize the return value.
>
>A new patch, with small sanity tests added.
>
>2016-10-15  Ville Voutilainen  <ville.voutilainen@gmail.com>
>
>    Make sure the return value of malloc_allocator::allocate
>    is zero-initialized so that checking it for non-zero works
>    later.
>    * include/ext/malloc_allocator.h (malloc_allocator::allocate):
>    Initialize the return value.
>    * testsuite/ext/malloc_allocator/sanity.cc: New.

Oops, thanks for catching that. OK for trunk.



More information about the Gcc-patches mailing list