public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antomicx at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/49863] -Wunused-result not behaving correctly
Date: Wed, 27 Jul 2011 10:30:00 -0000 [thread overview]
Message-ID: <bug-49863-4-sCfOLDvcb4@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
--- Comment #2 from antomicx at gmail dot com 2011-07-27 10:29:46 UTC ---
(In reply to comment #1)
> Because glibc annotates system with the attribute only if you use
> -D_FORTIFY_SOURCE=1 or higher, and then only if optimization is enabled:
I got it. Just out of curiosity, is this feature documented somewhere (apart
from source code, obviously ;-) )?
Thanks!
next prev parent reply other threads:[~2011-07-27 10:30 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 [this message]
2012-05-23 17:21 ` jim.king at simplivity dot com
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-sCfOLDvcb4@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).