From: Yale Zhang <yzhang1985@gmail.com>
To: java@gcc.gnu.org
Subject: add support for x86_64-w64-mingw32 and cut the fat from libgcj
Date: Sun, 24 Dec 2017 19:44:00 -0000 [thread overview]
Message-ID: <CALQF7ZxMGdFEYLfknXJRavDYEKWDxuYwcrX51EjAS7NooJvvRg@mail.gmail.com> (raw)
Greetings. I have a patch that allows GNU java to target MingW64
(host=GNU/Linux only). Are you guys still taking patches now that Java
has been removed from GCC 7? Or would it be more appropriate to host
it on my own website or instructables.com?
I also have another patch that cuts all the GUI, cryptography, and non
UTF8/16 charset support from libgcj. This reduces the size of
statically linked EXEs a lot (~27MiB to 4.5 MiB for a hello world
program). This is important for a legacy utility that other developers
use on Windows and who don't want to install a Java runtime.
Commenting out and deleting code is a crude way to do, I know. Should
use conditional compilation and even explore what's causing GUI code
to be dragged into a hello world program. Maybe dead code removal
isn't working (need to compile with -ffunction-sections and
--gc-sections?)
appreciate your feedback,
-Yale
next reply other threads:[~2017-12-24 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 19:44 Yale Zhang [this message]
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
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=CALQF7ZxMGdFEYLfknXJRavDYEKWDxuYwcrX51EjAS7NooJvvRg@mail.gmail.com \
--to=yzhang1985@gmail.com \
--cc=java@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).