Jeffrey A Law <[EMAIL PROTECTED]> writes:

> We clearly disagree then.  Though my 15+ years of working with GCC I've
> seen far more complaints about false positives than missing instances
> of this warning.

I think that most of the false positives are of the form

    int x, f, y;
    f = foo ();
    if (f)
      x = 1;
    y = g ();
    if (f)
      y = x;
    return y;

Here presumably we can all agree that gcc ideally should not warn that
x may be used uninitialized.

Ian

Reply via email to