public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8994: [3.2/3.3 regression] ICE with -O -march=pentium4 Date: Wed, 18 Dec 2002 13:16:00 -0000 [thread overview] Message-ID: <20021218211602.2241.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8994; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: "Joseph S. Myers" <jsm28@cam.ac.uk> Cc: gcc-gnats@gcc.gnu.org Subject: Re: optimization/8994: [3.2/3.3 regression] ICE with -O -march=pentium4 Date: Wed, 18 Dec 2002 15:08:46 -0600 (CST) On Wed, 18 Dec 2002, Joseph S. Myers wrote: > On 18 Dec 2002, Wolfgang Bangerth wrote: > > > I may be blind, but if I remember right then a compound statement is a > > ({...}) thing, of which there is exactly one, and it does not have a label > > at its end. However, this warning is given by all gcc versions I checked. > > No, that's a statement expression, which contains a compound statement. > A compound statement is simply { ... }. Oh, sorry, then I was confused. Still, the testcase is ---------------------------- typedef union { double value; int lsw; } astr; void js_dtoa(double d) { while(1) if (( { astr sh_u; sh_u.value = d; sh_u.lsw; }) & 1) goto ret; ret: } --------------------------- Why is it warning about this: tmp/regression/test/PR8994.c: In function `js_dtoa': tmp/regression/test/PR8994.c:12: warning: deprecated use of label at end of compound statement The compound statement is then actually the function body, and this seems like a pretty common technique. Also, saying deprecated means that it is either deprecated by the standard, or it is illegal but accepted by gcc as an extension. It is the latter, right, since a label must be followed by another statement, and be it only ";". W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-18 21:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-18 13:16 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-18 16:36 Janis Johnson 2002-12-18 13:46 Joseph S. Myers 2002-12-18 13:16 Volker Reichelt 2002-12-18 13:06 Joseph S. Myers 2002-12-18 12:56 Wolfgang Bangerth 2002-12-18 12:46 Torbjorn Wassberg 2002-12-18 12:23 bangerth
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=20021218211602.2241.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).