This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/5035] Incorrectly produces '`<var>' might be used uninitialized in this function'
- From: "pinskia at physics dot uc dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Dec 2005 14:22:30 -0000
- Subject: [Bug tree-optimization/5035] Incorrectly produces '`<var>' might be used uninitialized in this function'
- References: <bug-5035-1331@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #11 from pinskia at gcc dot gnu dot org 2005-12-22 14:22 -------
Subject: Re: Incorrectly produces '`<var>' might be used uninitialized in this
function'
On Dec 22, 2005, at 5:38 AM, trick at icculus dot org wrote:
>
>
> ------- Comment #10 from trick at icculus dot org 2005-12-22 10:38
> -------
> Maybe you could add a new variable attribute so that these warnings
> could at
> least be avoided in cases where the coder knows the code is correct ?
> Something like:
>
> int x __attribute__((__notuninited__));
int x = x;
Will make the warning go away, plus this is documented in the options
section
under -Winit-self.
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5035