[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

[manu at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856

Manuel López-Ibáñez manu at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||manu at gcc dot gnu.org
 Resolution|--- |DUPLICATE

--- Comment #6 from Manuel López-Ibáñez manu at gcc dot gnu.org ---
The infamous PR18501

*** This bug has been marked as a duplicate of bug 18501 ***

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

[gang.chen at asianux dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856

Chen Gang gang.chen at asianux dot com changed:

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED

--- Comment #7 from Chen Gang gang.chen at asianux dot com ---
(In reply to Manuel López-Ibáñez from comment #6)
 The infamous PR18501
 
 *** This bug has been marked as a duplicate of bug 18501 ***

Thanks.

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856

--- Comment #1 from Andrew Pinski pinskia at gcc dot gnu.org ---
I think this is a dup of another bug.

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

[gang.chen at asianux dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856

Chen Gang gang.chen at asianux dot com changed:

   What|Removed |Added

 CC||gang.chen at asianux dot com

--- Comment #2 from Chen Gang gang.chen at asianux dot com ---
Created attachment 30478
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30478action=edit
Compiling command(use red hat 4.7.2 as a demo), it's same for gcc 4.9.0
compiling from source code.

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

[gang.chen at asianux dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856

--- Comment #3 from Chen Gang gang.chen at asianux dot com ---
Created attachment 30479
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30479action=edit
The related warnings, not find uninitailized warning for lru.

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

[gang.chen at asianux dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856

--- Comment #4 from Chen Gang gang.chen at asianux dot com ---
Created attachment 30480
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30480action=edit
This attachment is for gcc 4.9.0 from compiling source code (sorry, the
original disassembly code is for red hat 4.7.2)

[Bug middle-end/57856] for an uninitialized variable, gcc assumes it already has value instead of report uninitialized warnings.

[gang.chen at asianux dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57856

--- Comment #5 from Chen Gang gang.chen at asianux dot com ---
(In reply to Andrew Pinski from comment #1)
 I think this is a dup of another bug.

Firstly, thank you reply as soon as possible.

Could you provide the related Bug number ?

Thanks.