From: Andrew Haley <aph@redhat.com>
To: Mathieu Malaterre <mathieu.malaterre@gmail.com>
Cc: yuri@rawbw.com, java@gcc.gnu.org
Subject: Re: Is gcj dead?
Date: Mon, 19 Oct 2009 13:10:00 -0000 [thread overview]
Message-ID: <4ADC6531.5000504@redhat.com> (raw)
In-Reply-To: <bf0c3b3f0910190606q26681634i13fd2d2273149aa3@mail.gmail.com>
Mathieu Malaterre wrote:
> On Mon, Oct 19, 2009 at 3:00 PM, Andrew Haley <aph@redhat.com> wrote:
>> Mathieu Malaterre wrote:
>>> On Sun, Oct 18, 2009 at 12:08 PM, Andrew Haley <aph@redhat.com> wrote:
>>>> Yuri wrote:
>>>>> Last news in http://gcc.gnu.org/java/ are dated March 2007.
>>>> Yes, we should update that. There hasn't been a lot of new gcj development,
>>>> but it is maintained.
>>>>
>>>>> Also I submitted few PRs a month ago and there is no response at all.
>>>> Which ones?
>>> How about this one:
>>>
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40816
>> I am still rather nervous about that one, as it's an ABI change.
>
> Point taken.
> In the long term this will prevent compilation of package such as VTK
> on debian on arch such as HPPA.
Really? That's all rather amazing. Is there no simple workaround?
> On those the JAVA implementation is
> GCJ. Hopefully by then OpenJDK-6 will compile on HPPA ...
> Can you set bug as won't fix or something like that ?
I should, I suppose.
Andrew.
next prev parent reply other threads:[~2009-10-19 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AD846B0.2080102@rawbw.com>
2009-10-18 10:08 ` Andrew Haley
2009-10-18 22:42 ` Yuri
2009-10-19 12:00 ` Andrew Haley
2009-10-19 12:42 ` Mathieu Malaterre
2009-10-19 13:01 ` Andrew Haley
2009-10-19 13:07 ` Mathieu Malaterre
2009-10-19 13:10 ` Andrew Haley [this message]
2009-10-19 13:25 ` Mathieu Malaterre
2009-10-19 16:03 ` Andrew Haley
2009-10-19 20:00 ` Joel Dice
2009-10-20 9:27 ` Andrew Haley
2009-10-20 14:07 ` Joel Dice
2009-10-20 14:17 ` Andrew Haley
2009-10-20 14:45 ` Joel Dice
2009-10-20 15:04 ` Joel Dice
2009-10-20 15:08 ` Andrew Haley
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=4ADC6531.5000504@redhat.com \
--to=aph@redhat.com \
--cc=java@gcc.gnu.org \
--cc=mathieu.malaterre@gmail.com \
--cc=yuri@rawbw.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).