From: Ricardo Wurmus <rekado@elephly.net>
To: Yale Zhang <yzhang1985@gmail.com>
Cc: Brian Jones <cbjones1@gmail.com>, java@gcc.gnu.org
Subject: Re: add support for x86_64-w64-mingw32 and cut the fat from libgcj
Date: Tue, 02 Jan 2018 10:04:00 -0000 [thread overview]
Message-ID: <87efn8aaa1.fsf@elephly.net> (raw)
In-Reply-To: <CALQF7ZxNf=FON4AH4v5nw+V+yEP7JpOTToejt3ABVUhRx7usNA@mail.gmail.com>
Yale Zhang <yzhang1985@gmail.com> writes:
> "I was hoping to keep GCJ up to date to use it for OpenJDK bootstrapping"
> That paranoid? Why not use the minimal Eclipse Java compiler which
> Classpath uses for bootstrapping? It sounds like ECJ can't be trusted if it
> was compiled with an untrusted/unknown compiler.
ECJ is a binary blob, and you need some pre-compiled Classpath binaries.
For GNU Guix we bootstrap the JDK with Jikes, SableVM, various versions
of GNU Classpath, and an older version of ECJ built from source. The
details can be found here:
http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/java.scm#n68
GCJ was no good bootstap compiler as it included a pre-built copy of
Classpath.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-01-02 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 19:44 Yale Zhang
2017-12-25 0:33 ` R0b0t1
2017-12-25 4:58 ` Yale Zhang
2017-12-27 3:00 ` R0b0t1
2018-01-01 3:42 ` Andrew Hughes
2018-01-01 9:00 ` Andrew Haley
2018-01-01 10:38 ` Brian Jones
2018-01-01 21:03 ` Yale Zhang
2018-01-02 9:58 ` Andrew Haley
2018-01-02 10:00 ` Andrew Haley
2018-01-02 10:04 ` Ricardo Wurmus [this message]
2017-12-24 19:46 Yale Zhang
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=87efn8aaa1.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=cbjones1@gmail.com \
--cc=java@gcc.gnu.org \
--cc=yzhang1985@gmail.com \
/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).