> 
> 
> There's more to it than that, unless your compiler is very broken.
> GCC should not warn for "int x; foo (&x);".

Or inlining happened and foo got inlined and really there is a path
which could leave x uninitialized.

-- Pinski

Reply via email to