This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug middle-end/20644] bogus uninitialized warning on unused variable



------- Comment #4 from h dot b dot furuseth at usit dot uio dot no  2005-11-02 19:52 -------
I think I'd appreciate that warning when writing portable code:

The warning can be useful if the 1 is replaced with a macro
which may or may not expand to 1, or an enum defined in an #ifdef,
or an implementation-dependent expression like ((char)-1 < 0).

But of course, it depends on how many false positives the warning
tends to give for normal programs.

Maybe there could be a warning option to turn on and off some
warnings that do not apply with the particular #defines and
constants being used.  (And also turn on/off -Wunreachable
for this case.)


-- 

h dot b dot furuseth at usit dot uio dot no changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |h dot b dot furuseth at usit
                   |                            |dot uio dot no


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]