public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: trt@sas.com To: gcc-gnats@gcc.gnu.org Subject: c/7543: Suggest new warning message for gcc Date: Thu, 08 Aug 2002 09:16:00 -0000 [thread overview] Message-ID: <20020808160543.6510.qmail@sources.redhat.com> (raw) >Number: 7543 >Category: c >Synopsis: Suggest new warning message for gcc >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Thu Aug 08 09:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Tom Truscott >Release: gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81) >Organization: >Environment: >Description: gcc currently does not warn about the logic error in the following program: int subr(int flags) { return (!flags & 0x80) ? 1 : 0; } It should have been (!(flags & 0x80)) >How-To-Repeat: Compile the above program, with -W -Wall, whatever. No warning message. >Fix: A patch to gcc which gives a warning in this situation appears in http://gcc.gnu.org/ml/gcc-patches/2002-06/msg01523.html >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-08 16:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-08 9:16 trt [this message] 2003-03-07 2:48 bangerth 2003-03-10 20:50 bangerth 2003-03-10 20:56 Wolfgang Bangerth
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=20020808160543.6510.qmail@sources.redhat.com \ --to=trt@sas.com \ --cc=gcc-gnats@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).