This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/11613] attribute unused after label causes error with g++
- From: "pinskia at physics dot uc dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Jul 2003 14:33:25 -0000
- Subject: [Bug c++/11613] attribute unused after label causes error with g++
- References: <20030721100002.11613.jsaw@gmx.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11613
pinskia at physics dot uc dot edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2003-07-21 14:33:25
date| |
------- Additional Comments From pinskia at physics dot uc dot edu 2003-07-21 14:33 -------
>From <http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html>:
An attribute specifier list may appear __after__ the __colon__ following a label, other than a case or
default label. The only attribute it makes sense to use after a label is unused. This feature is
intended for code generated by programs which contains labels that may be unused but which is
compiled with -Wall. It would not normally be appropriate to use in it human-written code,
though it could be useful in cases where the code that jumps to the label is contained within an
#ifdef conditional.
Also from that page:
Because of infelicities in the grammar for attributes, some forms described here may not be
successfully parsed in all cases
I do not know if this should be acceptable in c++.