Re: Quiet valgrind warnings in init_current_teb

[Alexandre Julliard]

"Mike Hearn"  writes:
> ent is initialized here OK, it's correctly pointing to an LDT_ENTRY
> struct on the stack. Valgrind is (presumably) complaining about
> ent->HighWord.Bits.Granularity being tested before being assigned, but
> that's wrong and is either a mistake in:
>
> a) My thinking (quite likely)
> b) Valgrind
> c) GCC

It's a valgrind bug. There are some uninitialized bits in the
variable, but the bit that the code is testing is initialized
properly.