It is redundant to check x*alloc's return value for null pointers, since they are guaranteed to either return non-NULL or terminate the program. In cases where we memset the malloc'd memory to 0, we can more efficiently use the xzalloc() routine. zalloc looks for opportunities to return memory chunks that have already been zero'd out, so it can provide better performance. This patch addresses this warning, reported by Denis Denisov: [clients/window.c:1164] -> [clients/window.c:1166]: (warning) Possible null pointer dereference: surface - otherwise it is redundant to check it against null. [clients/window.c:4513] -> [clients/window.c:4514]: (warning) Possible null pointer dereference: surface - otherwise it is redundant to check it against null. Signed-off-by: Bryce Harrington <bryce@osg.samsung.com> Reviewed-by: Marek Chalupa <mchqwerty@gmail.com>dev
parent
430aee1c23
commit
da9d8fa3e4
Loading…
Reference in new issue