[PATCH] Check for null pointers in ubsan

Joerg Sonnenberger joerg at britannica.bec.de
Mon May 11 12:29:45 PDT 2015


On Mon, May 11, 2015 at 07:00:53PM +0000, Nuno Lopes wrote:
> gcc 4.9 just got more aggressive and is now exploiting the fact that
> input pointers to memcpy/memmove cannot be null (even if the size is 0).

Are you sure that this is GCC and not glibc? Can someone *please* raise
a defect report against the C standard? This is ridiculous...

Joerg



More information about the cfe-commits mailing list