------- Comment #3 from hjl at lucon dot org 2007-09-02 13:37 -------
> Subject: Re: New: Failed to warn uninitialized stack variable
>
>
> Not really because this is the same as
> bar (&frame.value[0]);
>
> Where bar can do pointer tricks to get back to original struct and
> then change prev, trust me, this is allowed. There is a comment in
> GCC sources about this specific issue.
>
How does bar know it is called by
bar (frame.value);
not
mpz_t value;
...
bar (value);
--
hjl at lucon dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33279
