Dalibor Topic wrote:
Dalibor Topic wrote:
Robert Schuster wrote:
Hi,
Robert Schuster schrieb:
I now found a cacheflush implementation in libffi. I adjust this for
kaffe and report back.
I took what was said here[0] as a base for an OABI- EABI-compliant
implementation of the cache flushing.
Dalibor Topic schrieb:
Dalibor Topic wrote:
Dalibor Topic wrote:
My plan would be to look at making the interpreter pass on arm-oabi
and arm-eabi without failures, and then
to move on to the jits. I'd also like to see if I can rip out all
the atomic* code in Kaffe's config dirs by using
Dalibor Topic wrote:
Dalibor Topic wrote:
My plan would be to look at making the interpreter pass on arm-oabi
and arm-eabi without failures, and then
to move on to the jits. I'd also like to see if I can rip out all the
atomic* code in Kaffe's config dirs by using glib's
atomic functions
On Fri, 2008-02-08 at 00:26 +0100, Dalibor Topic wrote:
I've looked a bit closer at the 3 ARM OABI errors, in particular at the
errors in test/regression/DoubleConst.java . That test fails because we
get the bitstreams of the doubles being tested when we call
Double.doubleToLongbits with
Dalibor Topic wrote:
Dalibor Topic wrote:
My plan would be to look at making the interpreter pass on arm-oabi
and arm-eabi without failures, and then
to move on to the jits. I'd also like to see if I can rip out all the
atomic* code in Kaffe's config dirs by using glib's
atomic functions
Wow, you did it by yourself...
Dalibor Topic wrote:
Dalibor Topic wrote:
Dalibor Topic wrote:
My plan would be to look at making the interpreter pass on arm-oabi
and arm-eabi without failures, and then
to move on to the jits.
Yes, in general tackling interpreter version first is a good
Dalibor Topic wrote:
My plan would be to look at making the interpreter pass on arm-oabi
and arm-eabi without failures, and then
to move on to the jits. I'd also like to see if I can rip out all the
atomic* code in Kaffe's config dirs by using glib's
atomic functions instead, as that would be
Dalibor Topic schrieb:
Dalibor Topic wrote:
Robert Schuster wrote:
Hi.
Dalibor Topic schrieb:
On to the next problem: currently the jit regression test fails at a
floating point test.
The FAQ.arm says:
From Kaffe's point of view, only 'FPA' is supported right now. Some
effort has been
Hi.
Dalibor Topic schrieb:
On to the next problem: currently the jit regression test fails at a
floating point test.
The FAQ.arm says:
From Kaffe's point of view, only 'FPA' is supported right now. Some
effort has been started to use 'VFP', and I hope we can rewrite this
section soon. For
Robert Schuster wrote:
Hi.
Dalibor Topic schrieb:
On to the next problem: currently the jit regression test fails at a
floating point test.
The FAQ.arm says:
From Kaffe's point of view, only 'FPA' is supported right now. Some
effort has been started to use 'VFP', and I hope we can rewrite
Dalibor Topic wrote:
Robert Schuster wrote:
Hi.
Dalibor Topic schrieb:
On to the next problem: currently the jit regression test fails at a
floating point test.
The FAQ.arm says:
From Kaffe's point of view, only 'FPA' is supported right now. Some
effort has been started to use 'VFP', and I
Dalibor Topic wrote:
Robert Schuster wrote:
Hi,
Robert Schuster schrieb:
I now found a cacheflush implementation in libffi. I adjust this for
kaffe and report back.
I took what was said here[0] as a base for an OABI- EABI-compliant
implementation of the cache flushing.
It compiles nicely
Robert Schuster wrote:
Hi,
Robert Schuster schrieb:
I now found a cacheflush implementation in libffi. I adjust this for
kaffe and report back.
I took what was said here[0] as a base for an OABI- EABI-compliant
implementation of the cache flushing.
It compiles nicely (I can only test the
Hi,
Robert Schuster schrieb:
I now found a cacheflush implementation in libffi. I adjust this for
kaffe and report back.
I took what was said here[0] as a base for an OABI- EABI-compliant
implementation of the cache flushing.
It compiles nicely (I can only test the EABI-variant here).
Hi,
talking to Dalibor on IRC he said there are some interesting compiler
warnings in my build and he is going to look at them.
Robert Schuster schrieb:
kaffe-bin: exception.c:100: vmExcept_setJNIFrame: Assertion `fp !=
(JNIFrameAddress)0'
Perhaps a backtrace for this is of interest:
#0
Hi,
its me again.
Robert Schuster schrieb:
#0 0x40042a38 in vmExcept_setJNIFrame ()
from /usr/lib/kaffe/jre/lib/arm/libkaffe-1.1.9-pre.so
#1 0x4004f1bc in KaffeVM_safeCallMethodA ()
from /usr/lib/kaffe/jre/lib/arm/libkaffe-1.1.9-pre.so
#2 0x4003a0ec in processClass ()
from
Hi Robert,
I just tried to cross-compile kaffe for ARM (I read the FAQ :) ). The
It's good to hear from someone that FAQ.cross-compiling is useful ;-)
target (and toolchain) is GNU EABI which is not officially supported in
kaffe. So perhaps my compile error is just because of that - I get this:
Kiyo Inaba wrote:
Hi Robert,
I just tried to cross-compile kaffe for ARM (I read the FAQ :) ). The
It's good to hear from someone that FAQ.cross-compiling is useful ;-)
target (and toolchain) is GNU EABI which is not officially supported in
kaffe. So perhaps my compile error is just
[EMAIL PROTECTED] wrote:
Hi...all.
I want to cross compile for arm architecture.
But, When configuring, saw the error messages.
[EMAIL PROTECTED] kaffe-1.1.4]# CC=arm-linux-gcc NM=arm-linux-nm
AR=arm-linux-ar
./configure --host=arm-linux --build=i686-linux
checking for a BSD-compatible
19 matches
Mail list logo
