After the regression and retry for inlining, I will try to install
linux on 68040 machine. If you remember, this CPU has different way
for cache and may introduce some problem with JIT.
yes, 68030 and 68040 are different wrt to cache. old opensd2/jit.h had #
ifdef's for that
Kiyo
P.S. The
Hi Kiyo,
Kiyo Inaba wrote:
Dalibor,
My earlier patch I posted is just to verify where we have
problems. I am still thinking whether macro version is better
or switch to inlining.
Any idea?
I'd rather have it inlined, since inlining implies better type checking
from the compiler, more meaningful
I wrote:
OK, self compiling finished (after, say, 10 hours of configure/compiling)
and it started to compile javalib by using kjc. I attached a patch
against cvs-040408 (maybe ok for cvs-head also).
I tried twice but building 'rt.jar' stops at
In [EMAIL PROTECTED] Kiyo Inaba wrote:
BTW, one more question.
For m68k-linux, gcc complains that sysdepCallMethod can not be inlined
because of alloca. When the compilation finished, I will test whether
this kaffe works or not.
I cannot get kaffe to work on linux/m68k. Currently it builds
Riccardo wrote:
In [EMAIL PROTECTED] Kiyo Inaba wrote:
BTW, one more question.
For m68k-linux, gcc complains that sysdepCallMethod can not be inlined
because of alloca. When the compilation finished, I will test whether
this kaffe works or not.
I cannot get kaffe to work on linux/m68k.
Riccardo and m68k-linux lovers,
on 4/14/04 10:10 AM, Kiyo Inaba at [EMAIL PROTECTED] wrote:
I have slightly different behavior, but the result (kjc is not useable)
is same. Let me investigate more...
OK, self compiling finished (after, say, 10 hours of configure/compiling)
and it started to
Dalibor,
My earlier patch I posted is just to verify where we have
problems. I am still thinking whether macro version is better
or switch to inlining.
Any idea?
Kiyo
P.S. I can not test modified inlining version right now, because
it may take another several hours to finish compiling
