Fix a set of inverted conditionals for kernel validation.
Bug: http://b/25853842
A previous refactoring accidentally inverted the conditions here, using
|= instead of &= for a boolean that started as true. Whenever we would
get an invalid call, the |= meant that we would still retain our initial
true value (claiming that the incorrect code was valid). Luckily, other
subsequent checks would then cause the compilation to fail elsewhere
(usually by noticing that we had already queued up diagnostics). With
the increased checking for void * in Bug 25853842, a new test case
triggered a latent assertion that exposed this bug.
Change-Id: I85f4e6db64f5fc8eb0027c30c23dcee2dfaf9826
1 file changed
