Ether way, as it's a 1-bit field, the value can only be 0 or 1 and is always > -3.
For the second part of your comment, comparisons are always done between the same type. In this case, either the -3 is promoted to unsigned (which gives the result UINT_MAX - 2, a large positive number) or the bitfield is promoted to int. It is the rules for this type promotion that is the heart of the problem.
It's just astounding how many developer-years have been wasted by the industry's insistence on producing and accepting wrong answers when commodity hardware has been maintaining under/overflow flags for literally my entire career.
Conversion of out-of-range values to signed types is, however, implementation-defined (and also allows an implementation-defined signal to be raised, which in practice makes it something to avoid in correct programs).
http://stackoverflow.com/questions/50605/signed-to-unsigned-...
A computation involving unsigned operands can
never overflow, because a result that cannot be
represented by the resulting unsigned integer type
is reduced modulo the number that is one greater
than the largest value that can be represented by
the resulting unsigned integer type.But in general, uninitialized variables aren't even random in C. Accessing them is undefined. That means you aren't guaranteed to get a bogus value, you could just as well get a nasal demon.