From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3217 invoked by alias); 24 Feb 2004 14:35:39 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 3206 invoked by alias); 24 Feb 2004 14:35:38 -0000 Date: Tue, 24 Feb 2004 14:35:00 -0000 Message-ID: <20040224143538.3205.qmail@sources.redhat.com> From: "msp at nortelnetworks dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20011205204601.5026.bh@techhouse.brown.edu> References: <20011205204601.5026.bh@techhouse.brown.edu> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/5026] __attribute__ ((unused) seems misdocumented X-Bugzilla-Reason: CC X-SW-Source: 2004-02/txt/msg02293.txt.bz2 List-Id: ------- 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