public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mathieu dot malaterre at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/40816] error: 'jvariant::jvariant(jbyte)' cannot be overloaded
Date: Tue, 27 Oct 2009 09:43:00 -0000	[thread overview]
Message-ID: <20091027094321.2422.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40816-9357@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from mathieu dot malaterre at gmail dot com  2009-10-27 09:43 -------
Copying from the mailing list:


from    Andrew Haley <aph@redhat.com>
to      Tom Tromey <tromey@redhat.com>
cc      java@gcc.gnu.org
date    Mon, Oct 19, 2009 at 5:03 PM
subject Re: Is gcj dead?
mailing list    <java.gcc.gnu.org> Filter messages from this mailing list
unsubscribe     Unsubscribe from this mailing-list

hide details Oct 19 (8 days ago)

- Show quoted text -
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.

Andrew.


-- 

mathieu dot malaterre at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mathieu dot malaterre at
                   |                            |gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40816


  reply	other threads:[~2009-10-27  9:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21  8:44 [Bug java/40816] New: " mathieu dot malaterre at gmail dot com
2009-10-27  9:43 ` mathieu dot malaterre at gmail dot com [this message]
2010-01-22 11:43 ` [Bug java/40816] " mathieu dot malaterre at gmail dot com
2010-01-23 23:18 ` aph at redhat dot com
2010-02-24 15:34 ` aph at gcc dot gnu dot org
     [not found] <bug-40816-8172@http.gcc.gnu.org/bugzilla/>
2010-09-28 14:06 ` aph at gcc dot gnu.org

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=20091027094321.2422.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).