public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msp at nortelnetworks dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/5026] __attribute__ ((unused) seems misdocumented
Date: Tue, 24 Feb 2004 14:35:00 -0000 [thread overview]
Message-ID: <20040224143538.3205.qmail@sources.redhat.com> (raw)
In-Reply-To: <20011205204601.5026.bh@techhouse.brown.edu>
------- Additional Comments From msp at nortelnetworks dot com 2004-02-24 14:35 -------
Subject: Re: __attribute__ ((unused) seems misdocumented
Does that mean that there is no alternative way of tell gcc, in c++ mode,
that the label might not be used?
If so, I will raise a bug/enhancement request against bison suggesting
they change their usage to be #ifndef __cplusplus or something.
Cheers
Mark
On Tue, 24 Feb 2004, bangerth at dealii dot org wrote:
>
> ------- Additional Comments From bangerth at dealii dot org 2004-02-24 14:21 -------
> The reason why it is not allowed in C++ on labels has been stated
> several times: in C++, a variable declaration can follow a label,
> so the attribute that you want to attach to the label really goes
> to the next statement; gcc expects it to be a declaration, and
> complains if it can't find one.
>
> W.
>
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5026
next prev parent reply other threads:[~2004-02-24 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
[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
2011-03-01 10:21 ` rguenth 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=20040224143538.3205.qmail@sources.redhat.com \
--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).