public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/44677] Warn for variables incremented but not used Date: Mon, 28 Jun 2010 00:35:00 -0000 [thread overview] Message-ID: <20100628003458.11971.qmail@sourceware.org> (raw) In-Reply-To: <bug-44677-230@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2010-06-28 00:34 ------- Confirmed. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |diagnostic Last reconfirmed|0000-00-00 00:00:00 |2010-06-28 00:34:58 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44677
next prev parent reply other threads:[~2010-06-28 0:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-26 0:53 [Bug c/44677] New: " jsm28 at gcc dot gnu dot org 2010-06-28 0:35 ` pinskia at gcc dot gnu dot org [this message] [not found] <bug-44677-4@http.gcc.gnu.org/bugzilla/> 2020-05-19 17:23 ` [Bug c/44677] " msebor at gcc dot gnu.org 2021-04-21 17:41 ` jsm28 at gcc dot gnu.org 2021-10-24 6:09 ` pinskia at gcc dot gnu.org 2022-04-09 0:48 ` eggert at cs dot ucla.edu 2022-09-19 10:03 ` stormbyte at gmail dot com 2022-12-17 17:58 ` pinskia at gcc dot gnu.org
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=20100628003458.11971.qmail@sourceware.org \ --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).