public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0
Date: Thu, 28 Mar 2002 16:46:00 -0000 [thread overview]
Message-ID: <20020329004602.4978.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/5986; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: Jeff Sturm <jsturm@one-point.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0
Date: 28 Mar 2002 17:36:28 -0700
Jeff> I rebuilt the whole application from bytecode, 7 jar files
Jeff> containing some 1,018 class files... and it worked!
Excellent. I'll check it in at some point; we can always back it out
or refine it if need be.
Jeff> (Well, I had to use javac, since "gcj -C" caused verifier
Jeff> errors... but's that's another problem.)
Verifier errors from gcj itself? Unfortunately there are some known
`gcj -C' bugs. They're in Gnats. Fixing them looks complicated, and
I haven't had time to delve into it recently.
I'm curious why you're compiling to bytecode first.
Tom
next reply other threads:[~2002-03-29 0:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 16:46 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-28 17:26 Jeff Sturm
2002-03-28 16:41 tromey
2002-03-28 14:56 Alexandre Petit-Bianco
2002-03-28 14:06 Jeff Sturm
2002-03-27 16:56 Tom Tromey
2002-03-27 16:36 Alexandre Petit-Bianco
2002-03-27 15:06 Tom Tromey
2002-03-27 15:05 tromey
2002-03-27 13:26 Tom Tromey
2002-03-21 6:46 Jeff Sturm
2002-03-21 1:26 Bryce McKinlay
2002-03-20 17:26 Jeff Sturm
2002-03-20 15:46 Tom Tromey
2002-03-17 7:16 jsturm
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=20020329004602.4978.qmail@sources.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=tromey@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).