This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/33279] Failed to warn uninitialized stack variable
- From: "hjl at lucon dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Sep 2007 13:37:50 -0000
- Subject: [Bug middle-end/33279] Failed to warn uninitialized stack variable
- References: <bug-33279-682@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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