Work around compiler issue that confuses valgrind

For something like "if (a(&b) && b)", the compiler will generate code that
always checks both "b" and "a()", but then ignores "b" if "a()" returned
false. Since "b" is only initialized if "a()" returned true, the result is
valid, but confuses valgrind as it sees use of uninitialized memory.

Bug: 20950574
Change-Id: I1d173bbb32cc22f31d498f74677dc8be6bbe8df7