Re: shrinking clisp at build

Hi,

> * Mayuresh Kathe <[email protected]> [2017-10-09 22:09:18 +0500]:
>
> is it possible to shrink a clisp system during a from scratch build?
> i really don't need 'clos', 'ffi', "readline support" for the work i 
> intend to do, hence, believed it might be possible to improve 
> performance of the clisp system by making it smaller and lighter.

Are you sure you compiled CLISP the best possible way? It's possible that you
may get more performance benefits by tweaking C compilation settings (in the
5-10% range) rather than removing unused Lisp code.
 
E.g. does your build use a generational GC?
Did you compile with --enable-portability or some such killer?
Were optimizations enabled for every C source file? What about -DNO_ASM?

Of course, you can try and make the image a bit smaller by removing large parts
of CLOS, however that has become harder over time as CLISP uses more and more
CLOS internally (e. g. to dispatch streams).
20 years ago I successfully removed parts of the FORMATTER. This saved a little
memory, but only improved performance on a system without generational GC,
i.e. a stop, mark & sweep GC.

Good luck,
	Jörg Höhle

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list