public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@gcc.gnu.org
To: ebb9@email.byu.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	java-prs@gcc.gnu.org, nobody@gcc.gnu.org, tromey@gcc.gnu.org
Subject: Re: java/8051: Infinite loop after error reporting on extending final
Date: Sat, 02 Nov 2002 17:58:00 -0000	[thread overview]
Message-ID: <20021103015819.6962.qmail@sources.redhat.com> (raw)

Synopsis: Infinite loop after error reporting on extending final

Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Sat Nov  2 17:58:19 2002
Responsible-Changed-Why:
    I'm handling this
State-Changed-From-To: open->feedback
State-Changed-By: tromey
State-Changed-When: Sat Nov  2 17:58:19 2002
State-Changed-Why:
    I tried this with the current trunk.
    For me it reports the message and exits with status 1
    Can you try the trunk?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8051


             reply	other threads:[~2002-11-03  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02 17:58 tromey [this message]
2003-02-28  0:32 neroden

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=20021103015819.6962.qmail@sources.redhat.com \
    --to=tromey@gcc.gnu.org \
    --cc=ebb9@email.byu.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=java-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).