public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "scottwood at freescale dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/39731] New: Separate warning classes for maybe-uninitialized and known-uninitialized variables. Date: Fri, 10 Apr 2009 21:52:00 -0000 [thread overview] Message-ID: <bug-39731-16182@http.gcc.gnu.org/bugzilla/> (raw) It would be nice to provide separate -W flags for the "is used uninitialized" and "may be used uninitialized" variants of -Wuninitialized. The former is always a problem, while the latter is often noise. See this thread: http://ozlabs.org/pipermail/linuxppc-dev/2009-April/070540.html -- Summary: Separate warning classes for maybe-uninitialized and known-uninitialized variables. Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: scottwood at freescale dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39731
next reply other threads:[~2009-04-10 21:52 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-10 21:52 scottwood at freescale dot com [this message] 2009-04-16 18:28 ` [Bug middle-end/39731] " pinskia at gcc dot gnu dot org 2009-04-16 18:30 ` scottwood at freescale dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-39731-16182@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).