problems in compiler

Mark Evenson evenson at
Fri Mar 29 16:55:42 UTC 2019

> On Mar 15, 2019, at 09:13, Don Cohen <don-abcl at> wrote:
> --text follows this line--
> The version of ap5 from 2009 supposedly was able to build in the abcl
> of that time.  I'm now trying to make a more recent ap5 (but not
> very much changed) build in current abcl.  I've put the current source
> at under so that others who are willing to
> help can reproduce the problem.  Unfortunately I don't have a small 
> example, only a large one.

It took a little while to approach the AP5 code, but I managed to hack together
the attached patch for ABCL which allows the AP5 build strategy to succeed.

I still don't fully understand the AP5 compilation procedure but somehow it
trips up a leaky abstraction in the ABCL compiler which computes 
SYSTEM::*FASL-UNINTERNED-SYMBOLS* as an alist as it finds uninterned symbols,
but then serializes it as a vector when finished.

The attached patch contains a provisional hack to the ABCL compiler which
computes the alist form from the vector form rather than signalling an error,
so in order to use ABCL with AP5, you will have to build ABCL from source.

To truly fix this one would have to understand the AP5 compilation strategy  better, and then probably adjust the compiler's use of specials.

I am unsure how this ever worked in the past, but 2009 was a long time ago,
even for ABCL.

Note that while I have filed [ticket 463][463] with regards to this issue, I am
not currently inclined to prioritize resolving this issue in the ABCL source without a distillation of a simple example outside the AP5 source. 


"A screaming comes across the sky.  It has happened before but there is nothing 
to compare to it now."

-------------- next part --------------
A non-text attachment was scrubbed...
Name: compiler-ap5.diff
Type: application/octet-stream
Size: 1278 bytes
Desc: not available
URL: <>
-------------- next part --------------

More information about the armedbear-devel mailing list