More on memq, a timing experiment



Richard Fateman wrote:
> Now what I do not understand is that before loading "orig.o", expand(h)$
> takes about 2.3 seconds.  So there is something about MY compiling of orig.o
> that produces slower code. Perhaps there is a prologue to compiling that I
> am
> not using.  Nor can I explain why the code -- which replaces memq with what
> I think
> is fully equivalent to memq, fails to run tests rtest2.
>
>
>   
I do not know if this is the cause of your problems, but I do know that 
not all of the dependencies have been worked out.  There used to be (and 
still are?) symbols that are defined as macros and then functions later 
(or vice versa).  Most of the time, compiling and loading a file is ok, 
but not always.

I would suggest, perhaps, removing all of the fasls and try (mk:defsys 
"maxima" :compile) to compile everything in order again.  But even this 
might have problems.  The current maxima build procedure compiles all 
the files and loads them up.  Then it loads them all up again before 
saving a core.  This was done to work around some issue.  I don't 
remember what the issue was.

Ray