From: llewelly@xmission.com
To: rscheng@computermail.net
Cc: gcc-help@gcc.gnu.org
Subject: Re: warning message in gcc 3.3, but not gcc 2.95
Date: Fri, 30 Apr 2004 03:43:00 -0000 [thread overview]
Message-ID: <s3rr7u6ku4u.fsf@xmission.xmission.com> (raw)
In-Reply-To: <20040430020511.21A6B7251@sitemail.everyone.net>
Raymond Cheng <rscheng@computermail.net> writes:
> To All:
>
> I recently installed gcc 3.3 onto my laptop while desktop still has the
> old gcc 2.95. And then I tried "testing" the compiler with one of my old
> code. The new gcc gives
>
> warning: deprecated use of label at end of compound statement
[snip]
'depercated' in a warning is issued for a gcc extension which will be
removed in some future rlease. For example, with gcc 3.4.0, this
code:
int main()
{
foo:
}
results in this error message:
label_at_compound_statement_end.c: In function 'main':
label_at_compound_statement_end.c:5: error: label at end of compound
statement
If you place a semi-colon after the label warning (error with 3.4)
vanishes. ISO C requires a semi-colon after the label.
prev parent reply other threads:[~2004-04-30 3:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 2:05 Raymond Cheng
2004-04-30 3:43 ` llewelly [this message]
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=s3rr7u6ku4u.fsf@xmission.xmission.com \
--to=llewelly@xmission.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rscheng@computermail.net \
/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).