Tom Lane wrote:
> I asked some gcc experts at Red Hat about the new variable-may-be-used-
> uninitialized warnings that gcc 4.x reports. These occur in cases
> like
>
> int i, j;
> ...
> foo(&i, &j);
> // use i and j
>
> I had thought that gcc was being stricter about
I asked some gcc experts at Red Hat about the new variable-may-be-used-
uninitialized warnings that gcc 4.x reports. These occur in cases
like
int i, j;
...
foo(&i, &j);
// use i and j
I had thought that gcc was being stricter about the possibility that the
ca
