From: Andrew Haley <aph@redhat.com>
To: Joel Dice <dicej@mailsnare.net>
Cc: java@gcc.gnu.org
Subject: Re: Is gcj dead?
Date: Tue, 20 Oct 2009 14:17:00 -0000 [thread overview]
Message-ID: <4ADDC667.2050401@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0910200750090.13499@jdpc.ecovate.com>
Joel Dice wrote:
> On Tue, 20 Oct 2009, Andrew Haley wrote:
>
>> Joel Dice wrote:
>>> On Mon, 19 Oct 2009, Andrew Haley wrote:
>>>
>>>> Mathieu Malaterre wrote:
>>>>> On Mon, Oct 19, 2009 at 3:10 PM, Andrew Haley <aph@redhat.com> wrote:
>>>>>> 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?
>>>>>
>>>>> Compilation error can be found here:
>>>>>
>>>>> http://www.vtk.org/pipermail/vtk-developers/2009-June/006110.html
>>>>>
>>>>> And source:
>>>>>
>>>>> http://public.kitware.com/cgi-bin/viewcvs.cgi/Graphics/vtkJVMManager.h?view=annotate
>>>>>
>>>>>
>>>>>
>>>>> I really do not see how I can work around that. Simply removing one of
>>>>> the multiple signature is not a solution IMHO.
>>>>
>>>> Yes, I see what's going on.
>>>>
>>>> To Tom Tromey: This is an ABI change, but AFAICS the only time it makes
>>>> a difference is where it's already broken. I'm tempted to make the
>>>> change
>>>> now.
>>>
>>> On the subject of ABI bugs, perhaps this patch is also ready for prime
>>> time:
>>>
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28474
>>
>> I don't understand the comment
>>
>> "I will attach a patch which fixes the first case but not the second
>> (since I'm
>> not sure how the second case was intended to be handled)."
>>
>> What second case is that?
>
> Sorry it's not clear. The "second case" refers to the xy__User symbol
> in the example program, which is not fixed by the patch because it
> includes the sequence "__U". Only the first case, in which the
> underscores and "U" are not consecutive, is fixed.
OK.
>> BTW, if this patch had been submitted to java-patches at the time it
>> would have
>> gone straight in.
>
> I submitted it to gcc-patches@gcc.gnu.org (at your request) over two
> years ago:
>
> http://gcc.gnu.org/ml/java/2007-04/msg00007.html
> http://gcc.gnu.org/ml/gcc-patches/2007-04/msg00015.html
>
> I didn't realize that it also needed to go to java-patches.
Oh no, I'm really sorry. This was my fault, I simply forgot.
It seems that I was waiting for a complete patch, but one never arrived.
Any patch that goes in now really must be correct and complete, though.
I'll have a look now.
Andrew.
next prev parent reply other threads:[~2009-10-20 14:17 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
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 [this message]
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=4ADDC667.2050401@redhat.com \
--to=aph@redhat.com \
--cc=dicej@mailsnare.net \
--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).