public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: libgcj/10746: [3.3 regression] garbage collection crash in GCJ
Date: Mon, 12 May 2003 18:19:00 -0000	[thread overview]
Message-ID: <20030512181602.28058.qmail@sources.redhat.com> (raw)

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

From: =?iso-8859-1?Q?=D8yvind_Harboe?= <oyvind.harboe@zylin.com>
To: "'Dara Hazeghi'" <dhazeghi@yahoo.com>, <aph@redhat.com>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: RE: libgcj/10746: [3.3 regression] garbage collection crash in GCJ
Date: Mon, 12 May 2003 20:02:58 +0200

 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D=
 g
 cc&pr=3D10746
 >=20
 > Hello,
 >=20
 > FWIW, I don't seem to be able to get this under i686-linux. Hmm... =20
 > Using 3.2, 3.3 branch (20030511) or mainline (20030511), I=20
 > get: /tmp/dara/bin/gcj --main=3DTest Test.class -o test Test$1.class
 > Test.class:0: warning: source file seen twice on command line=20
 > and will =20
 > be compiled only once
 >=20
 > Are you _sure_ this problem still occurs with current sources=20
 > (or am I  doing something really dumb in trying to reproduce it)?
 Thanks,
 
 I know for sure that it is much harder to reproduce under Linux, ref.
 Ranjits
 posting.
 
 I'm waiting for Mohans next GCJ 3.3 build to test more. The build I ran
 was:
 
 http://www.thisiscool.com/gcc33_mingw.htm
 
 =D8yvind
 


             reply	other threads:[~2003-05-12 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 18:19 Øyvind Harboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 17:36 Dara Hazeghi
2003-05-12 12:32 steven

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=20030512181602.28058.qmail@sources.redhat.com \
    --to=oyvind.harboe@zylin.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).