On Fri, 6 Aug 2004 at 07:06:49 -0400, Larry Clapp wrote:
> I've gotten the same error. I got a clean compile after commenting out
> '(load (compile-file "jvm.lisp"))'. CVS from 8/6, ~6:50am EST.
> % java -version -server
> java version "1.4.1"
> Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01)
> Java HotSpot(TM) Server VM (build Blackdown-1.4.1-01, mixed mode)
> Same error at work with CVS from 8/2, same fix: comment (load
> (compile-file "jvm.lisp")).
> % java -version:
> java version "1.4.1"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
> Classic VM (build 1.4.1, J2RE 1.4.1 IBM build cxia321411-20030930 (JIT
> enabled: jitc))
OK, that's an interesting data point. If you load the compiled version
of the compiler, you've got trouble. If you don't, meaning you're
sticking with the interpreted version of the compiler, things work
> Debian GNU/Linux, kernel 2.6.6.
> One obvious difference is that you use jikes and we don't.
True enough, but the compiler doesn't use jikes; it generates the
bytecode by itself.
Another obvious difference is that I normally use Java 1.5.
So, I've just rebuilt the .java files with Javac (from Sun 1.4.2_03, as
it happens), fired up abcl with Blackdown 1.4.2-rc1, and run COMPILE-
SYSTEM with nary a hiccup.
Of course, the version of jvm.lisp that I'm using is different from
what's in CVS, and I have no idea what version you guys are using.
BTW, there's a line near the top of the file that tells you:
$Id: jvm.lisp,v 1.267 2004/08/05 02:35:34 piso Exp $
And indeed, it might be useful to mention the version of jvm.lisp
you're using when you report a compiler problem.
But in any case, I still can't reproduce the problem you guys are
seeing, and I know at least some other people have gotten things to
work (I'm assuming Andras has or he would have said something, and
Cristian Pietsch was able to get abcl to run cl-bench).
I do seem to recall that for a little while (maybe sometime last
weekend), the compiler worked OK for me if I loaded jvm.lisp, but was
broken if I compiled jvm.lisp and loaded jvm.abcl. I can't remember
what the problem was, or what I did to fix it, or whether I ever
checked it in in that broken state. (On a good day, I might fix a dozen
compiler bugs and introduce a dozen new ones, so it's hard for me to
keep all the details in mind.)
My best suggestion is to check back later, and in the meantime, Larry's
trick of commenting out (load (compile-file "jvm.lisp")) sounds like a