public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jim.king at simplivity dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/49863] -Wunused-result not behaving correctly
Date: Wed, 23 May 2012 17:21:00 -0000 [thread overview]
Message-ID: <bug-49863-4-N7DUFESoPg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49863-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49863
James E. King, III <jim.king at simplivity dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jim.king at simplivity dot
| |com
--- Comment #3 from James E. King, III <jim.king at simplivity dot com> 2012-05-23 17:15:46 UTC ---
I would like to recommend that this issue be re-opened. By leaving this issue
alone, debug and optimized builds behave differently. I would like to have the
same warnings enabled for both debug and optimized builds, and currently the
only way to do that is to disable the unused result code checking for the
release build. This seems counter-productive. If I declare
-D_FORTIFY_SOURCE=2 on the command line, the headers should not override me
just because it is not an optimized build. Is there some other unforeseen
reason for this rule, such as that the compiler actually cannot check for this
warning unless doing optimizations?
next prev parent reply other threads:[~2012-05-23 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 10:07 [Bug c/49863] New: " antomicx at gmail dot com
2011-07-27 10:20 ` [Bug c/49863] " rguenth at gcc dot gnu.org
2011-07-27 10:30 ` antomicx at gmail dot com
2012-05-23 17:21 ` jim.king at simplivity dot com [this message]
2012-05-23 17:27 ` 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=bug-49863-4-N7DUFESoPg@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: link
Be 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).