Re: egcs1.1.1 bogus warning: "might be used uninitialized"

["Brad M. Garcia" <bgarcia at fore dot com>]

On Wed, 10 Feb 1999, Jeffrey A Law wrote:

> Now, changing code in one function should not be changing the warnings gcc
> emits for an unrelated function *unless* the function changed is actually
> a template or is inlined.  If neither of those cases are true, then there's
> a serious bug that needs to be addressed.

In my case, this is plain C code, being compiled with gcc, not g++.
They are not templates, and are not inlined.

On the linux machine, both warnings were in the same function.
On sunos, the 3rd additional warning was in an unrelated function.

When I deleted some other, unrelated, functions from the file, the
warnings went away!  If instead, I initialized *one* of those
variables, then *all* the warnings would again go away.

So, yes, it looks like a serious bug.  But luckily the only consequence
appears to be bogus warning messages.  That's still a pain though,
since we always like to compile with -Wall -Werror.

Brad Garcia
   ___/  __ /  __ /  ___/ "Being the Linux of digital media
  __/   /  /  / _/  __/    would be a very good life."
_/    ____/ _/ _| ____/      - Jean-Louis Gassee, CEO of Be, Inc.