[EMAIL PROTECTED] writes:
> After upgrading to gcc-4.2.1 from a 3.4 version, I see that gcc now
> complains about uninitialized variables even when their address is
> passed to another function.
This should only happen when gcc can see the called function and see
that the value was used there bef
After upgrading to gcc-4.2.1 from a 3.4 version, I see that gcc now
complains about uninitialized variables even when their address is
passed to another function. Now that we get a warning about that
variable being possibly initialized, I'm forced to add an instruction
or two to initialize it (
