freenode/#sicl - IRC Chatlog
Search
16:18:33
beach
While working on this paper, I keep thinking that it would be preferable if code like this could be shared between implementations. And often the reason it can't be is that each implementation is bootstrapped differently.
16:18:34
beach
But then I was thinking whether it really matters how (say) ECL is bootstrapped. If not, it could be bootstrapped like SICL is, except that C code would be generated rather than an executable.
16:31:04
Bike
i thought about doing that with clasp for a while, but it's kind of annoying to generate llvm-ir without linking llvm, and being able to link C++ stuff like llvm is the point of the runtime
16:40:43
jackdaniel
currently ECL is built in three stages: ecl_min is built with C compiler (so core parts written in C are compiled), then all missing sources are loaded into bytecode vm (including clos and after that lisp->c compiler), and then all sources are compiled with lisp->c compiler (including itself)
16:41:50
jackdaniel
so, assuming that sicl-generated C code is part of ecl_min, then it call any preexisting functions from clos and I think it is not something you aim for with sicl
16:42:24
jackdaniel
alternative solution would be: ecl is built as it is now, and then a new version of clos is compiled and replaced