public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11613] attribute unused after label causes error with g++ Date: Wed, 23 Jul 2003 17:17:00 -0000 [thread overview] Message-ID: <20030723171739.11011.qmail@sources.redhat.com> (raw) In-Reply-To: <20030721100002.11613.jsaw@gmx.net> 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 ------- Additional Comments From nathan at gcc dot gnu dot org 2003-07-23 17:17 ------- label: __attribute__ ((whatever)) cannot be well formed g++, because, this is allowed __attribute__ ((unused)) int i; and so is label: int i; so what does label: __attribute__ ((unused)) int i; mean?
next prev parent reply other threads:[~2003-07-23 17:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-21 10:00 [Bug c++/11613] New: " jsaw at gmx dot net 2003-07-21 14:27 ` [Bug c++/11613] " bangerth at dealii dot org 2003-07-21 14:33 ` pinskia at physics dot uc dot edu 2003-07-21 15:01 ` bangerth at dealii dot org 2003-07-23 17:17 ` nathan at gcc dot gnu dot org [this message] 2003-07-23 17:23 ` nathan at gcc dot gnu dot org 2003-07-25 10:54 ` nathan at gcc dot gnu dot org 2004-02-24 17:04 ` msp at nortelnetworks dot com
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=20030723171739.11011.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: linkBe 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).