Robert Lougher gmail.com> writes:
>
> Hi Dalibor,
>
> Dalibor Topic kaffe.org> writes:
>
> > Kaffe uses its own sysdepCallMethod code but can also use libffi as an
> > additional option. See config/$arch/sysdepCallMethod.h for details. See
> > config/sysdepCallMethod-ffi.h for the wrapper for
Hi Dalibor,
Dalibor Topic kaffe.org> writes:
> Kaffe uses its own sysdepCallMethod code but can also use libffi as an
> additional option. See config/$arch/sysdepCallMethod.h for details. See
> config/sysdepCallMethod-ffi.h for the wrapper for ffi. Feel free to merge it
> into JamVM, if you thin
On Wed, Mar 16, 2005 at 05:40:22PM +0100, Wolfgang Baer wrote:
>
> From: Robert Lougher <[EMAIL PROTECTED]>
> To: Wolfgang Baer <[EMAIL PROTECTED]>
> Date: Wed, 16 Mar 2005 16:08:49 +
> Subject: Re: libbsf-java
>
> Hi again,
>
> > The statement of better choice is here maybe a bit out of co
Wolfgang Baer gmx.de> writes:
> The difficulty (once 64-bit support is done) with porting JamVM to
> these architectures is the calling convention. Other VMs (e.g.
> SableVM) rely on libffi to do this portably. I prefer to instead use
> hand-coded routines for each architecture/platform (using
--- Begin Message ---
Hi again,
> The statement of better choice is here maybe a bit out of context. gij,
> kaffe or sablevm are in the case of using the vm to BUILD a package for
> DEBIAN the (normally) only choice. But that has nothing to do with
> the quality or fitness for a given task of jam
5 matches
Mail list logo
