public inbox for
 help / color / mirror / Atom feed
From: Bryce McKinlay <>
To: Alan Eliasen <>
Subject: Re: Why GCJ won't load my plugin when compiling bytecode?
Date: Mon, 12 Sep 2011 09:32:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Sep 12, 2011 at 1:49 AM, Alan Eliasen <> wrote:
> On 09/09/2011 04:24 PM, Bryce McKinlay wrote:
>> Modern versions of gcj only compile .class files to object code. gcj
>> doesn't directly compile Java source code, nor generate bytecode.
>> (early versions of gcj did do these things, but it was changed years
>> ago)
>      Is this a permanent decision?  Is there any intention to make gcj
> compile from java source code again?
>   Can anyone give me pointers to where this was decided upon and announced?
>  I'm curious to see the discussion. :

January 8, 2007
We've merged the gcj-eclipse branch to svn trunk. The merge changes
gcj to use the Eclipse compiler as a front end, enabling all 1.5
language features. This merge also brings in a new, generics-enabled
version of Classpath, including some new tools. This new code will
appear in GCC 4.3.

June 6, 2006
RMS approved the plan to use the Eclipse compiler as the new gcj front
end. Work is being done on the gcj-eclipse branch; it can already
build libgcj. This project will allow us to ship a 1.5 compiler in the
relatively near future. The old gcjx branch and project is now dead.

      parent reply	other threads:[~2011-09-12  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09 20:57 Li junsong
2011-09-09 21:03 ` Andrew Pinski
2011-09-09 21:57   ` Li junsong
2011-09-09 22:24     ` Bryce McKinlay
2011-09-09 23:03       ` Li junsong
2011-09-12  0:49       ` Alan Eliasen
2011-09-12  0:54         ` Mark Mielke
2011-09-12  9:32         ` Bryce McKinlay [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).