public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/5026] __attribute__ ((unused) seems misdocumented
Date: Tue, 01 Mar 2011 08:51:00 -0000 [thread overview]
Message-ID: <bug-5026-4-F3U8TI7Gfk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-5026-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5026
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution| |FIXED
--- Comment #20 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-03-01 08:51:32 UTC ---
(In reply to comment #19)
> GCC documentation has been changed. __attribute__((unused)) on labels can be
> used in C++ code since GCC version 4.5.0. This PR should be closed probably.
The less, the merrier. Thanks!
(If you get a gcc.gnu.org account, you can do bug management:
http://gcc.gnu.org/svnwrite.html#authenticated)
next prev parent reply other threads:[~2011-03-01 8:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-5026-4@http.gcc.gnu.org/bugzilla/>
2011-03-01 6:42 ` d.g.gorbachev at gmail dot com
2011-03-01 8:51 ` manu at gcc dot gnu.org [this message]
2011-03-01 10:21 ` rguenth at gcc dot gnu.org
[not found] <20011205204601.5026.bh@techhouse.brown.edu>
2003-07-18 23:30 ` dhazeghi at yahoo dot com
2003-07-20 23:57 ` bje at wasabisystems dot com
2003-08-03 15:42 ` pinskia at physics dot uc dot edu
2003-08-03 15:47 ` neroden at gcc dot gnu dot org
2003-11-05 7:20 ` pinskia at gcc dot gnu dot org
2003-11-05 14:28 ` bh at techhouse dot brown dot edu
2004-01-31 20:29 ` pinskia at gcc dot gnu dot org
2004-02-24 13:37 ` msp at nortelnetworks dot com
2004-02-24 13:41 ` msp at nortelnetworks dot com
2004-02-24 14:21 ` bangerth at dealii dot org
2004-02-24 14:35 ` msp at nortelnetworks dot com
2004-02-24 14:52 ` bangerth at dealii dot org
2004-02-24 18:46 ` giovannibajo at libero dot it
2004-02-24 19:09 ` bangerth at dealii dot 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-5026-4-F3U8TI7Gfk@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).