A new warning in glibc triggers if memset is called with a constant size

of 0 (on the theory this is a mistake and the second and third arguments
were swapped). However the GCC inliner apparently is good enough that it
is triggering on code that just happens to create a zero length SecureVector
or equivalent - the constants get propagated so __builtin_constant_p returns
true.

Add an if(n) in clear_mem so we skip calling memset if the size is zero.

0 files changed, 0 insertions, 0 deletions