public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5941: incorrect "Unreachable statement" error
Date: Mon, 01 Apr 2002 16:56:00 -0000	[thread overview]
Message-ID: <20020402005600.3835.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/5941; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: Eric Blake <ebb9@email.byu.edu>
Cc: shroff@transeda.com, gcc-gnats@gcc.gnu.org, Per Bothner <per@bothner.com>
Subject: Re: java/5941: incorrect "Unreachable statement" error
Date: 01 Apr 2002 17:57:19 -0700

 >>>>> "Eric" == Eric Blake <ebb9@email.byu.edu> writes:
 
 Eric> for (int i = 0; ; i++) break;
 Eric> is legal, even though i++ will never be executed, because i++ is
 Eric> not a complete statement and is therefore not subject to the
 Eric> rules of JLS 14.20.
 
 Thanks for looking into this.  Unfortunately it looks difficult to fix
 the bug due to how loops are represented in gcj.
 
 One approach to fixing it would be to introduce a new FOR tree, which
 we could then handle specially in check-init.  Then later we would
 lower this FOR to a LOOP_EXPR.  We'll want to do something like this
 anyway for the AST work.
 
 Tom


             reply	other threads:[~2002-04-02  0:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-01 16:56 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-06 21:14 tromey
2002-04-25 11:47 tromey
2002-04-01 19:46 Per Bothner
2002-04-01 16:46 Eric Blake
2002-03-25 14:46 Eric Blake
2002-03-25 13:26 Tom Tromey
2002-03-13 12:56 Saurin B. Shroff
2002-03-13 12:16 Tom Tromey
2002-03-13 11:36 shroff

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=20020402005600.3835.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --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: 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).