public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: (Nathanael Nerode)
Subject: Re: GCC/GCJ versions?...
Date: Fri, 08 Aug 2003 15:56:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

>>>>> "Nathanael" == Nathanael Nerode <> writes:

Nathanael> I notice you're using the tree-ssa version of GCJ (with
Nathanael> extra patches?).  Is this essential, or is it possible to
Nathanael> use the mainline version which will become GCC 3.4?  If
Nathanael> mainline doesn't work, are the changes backportable?

Nathanael> It would certainly be nice if 3.4 could Do The Right Thing.

The gcc trunk would be fine.  The patches should back-port pretty

I'm going to start putting some of the patches in pretty soon.
Probably after next week.

There are some problems though.  First, I don't have the rationale for
a couple of the patches.  Maybe they're in the archives of our
internal mailing list; I'll look there, but if the info isn't there
then... ugh.  Maybe they'll turn out not to be necessary :-)

The miranda patch turns out to have a bug, which we discovered quite
recently.  If you apply it to the gcc trunk, I think you won't be able
to rebuild libgcj.  So that patch needs reworking.

And, finally, the patch to disable the gcj verifier is unacceptable.
But due to bugs in that verifier we can't compile eclipse with gcj.
Fixing it looks like quite a bit of work (hence all the discussion
about putting C++ into the front ends a while back...).  I'm not sure
when this will happen.  This is the most likely candidate for missing
the 3.4 timeline.


      reply	other threads:[~2003-08-08 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08  4:29 Nathanael Nerode
2003-08-08 15:56 ` Tom Tromey [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).