RE: [Gcl-devel] Re: new benchmark results for 8 CL implementations incliki.net

[Mike Thomas]

Thanks Christian.

| #0   FIND-METHOD-COMBINATION {loc0=#<compiled-closure
| 08846984>,loc1=and,loc2=nil,loc3=(#<compiled-closure 08...} [ihs=9]
| #1   ENSURE-GENERIC-FUNCTION-USING-CLASS {existing=(nil
| complex-method :lambda-list ...),spec=#S(pcl::method-call
| functio...} [ihs=8]
| #2   (DEFGENERIC COMPLEX-METHOD)2239 {loc0=complex-method,loc1=(a
| b &rest ...),loc2=(:method-combination (and)),loc3=...} [ihs=7]
| #3   CLCS-LOAD {} [ihs=6]
| #4   TOP-LEVEL
| {loc0=nil,loc1=nil,loc2=nil,loc3=#<compiled-function
| conditions::clcs-load>,loc4...} [ihs=5]
| #5   FUNCALL {loc0=#<compiled-function
| system:top-level>,loc1=nil,loc2=0,loc3=0,loc4=nil,loc5...} [ihs=4]
| NIL
| dbl:CL-BENCH.CLOS>>
| ---------->8---------------------
|
| May it be helpful.

Indeed.

I've started trawling through the PCL source and realise that I have a lot
to learn before I understand how that function was called by
ENSURE-GENERIC-FUNCTION-USING-CLASS, but your example seems to be caused in
a similar way to the previous report:

  http://lists.gnu.org/archive/html/gcl-devel/2003-07/msg00055.html

so it looks like this bug will be a good one to stomp on.  I'll let you know
if/when we manage to find it.

It will have to stand in line behind a more pressing problem which is
affecting the current Maxima release candidate unfortunately.

Cheers

Mike Thomas.