From: Andrew Haley <aph@redhat.com>
To: Yale Zhang <yzhang1985@gmail.com>, Brian Jones <cbjones1@gmail.com>
Cc: 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:00:00 -0000 [thread overview]
Message-ID: <a5b2476b-730c-5f94-2298-ffc1f84ce83e@redhat.com> (raw)
In-Reply-To: <CALQF7ZxNf=FON4AH4v5nw+V+yEP7JpOTToejt3ABVUhRx7usNA@mail.gmail.com>
On 01/01/18 21:03, Yale Zhang wrote:
> Alright, I've submitted my request & patch to bugzilla:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83647
I see it was rejected. We could create a GCJ 6 branch.
--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
next prev parent reply other threads:[~2018-01-02 10:00 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 [this message]
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=a5b2476b-730c-5f94-2298-ffc1f84ce83e@redhat.com \
--to=aph@redhat.com \
--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).