5:39:37vtomolebeach: To me, Common Lisp implementations are overwhelming. How is the back-end of SICL going? Are you still planning on compiling to x86_64? How much resources (time) does it take to write a "good" optimizing compiler?
5:42:52beachvtomole: The back-end is almost done. I have a separate repository containing an assembler for x86-64.
5:43:11beachvtomole: So, what's left is bootstrapping.
5:43:40beachvtomole: Also optimizations both at the HIR and at the MIR level must be improved.
5:44:25beachvtomole: Hard to say how long it takes. I am not working on it full time, so it is taking longer.
5:46:15vtomoleFor sure, a lot of implementors compile their languages to LLVM because they don't want to deal with writing optimizers. But you are not worried about performance being equal to SBCL are you?
5:47:20beachI am not afraid of writing optimizers. There are plenty of published algorithms.
5:47:32beachBut they have to be adapted to the specific case of Common Lisp.
5:47:47beachI don't think it is going to work to rely on LLVM for optimizations.
5:48:29beachIt doesn't know how to do things like type inference, path replication, escape analysis and other things that are crucial to Common Lisp performance.
5:48:59beachThings like that have to be done before low-level code is generated.
5:50:15beachI'm off to have breakfast. I'll be back in a little while.
13:43:52White_Flameebzzry: looking at usocket's lispworks backend, it looks like they're all in the comm: package https://github.com/usocket/usocket/blob/master/backend/lispworks.lisp
13:48:01oleodoes anyone know the error relating to the last link i provided
13:48:12oleothe former link is one where i dump an image from sbcl
13:48:48oleoit all goes ok, the image gets dumped but on start i get library error
13:49:31oleothe whole asdf mockery is because i have two copies of mcclim
13:49:49oleomcclim-master and mcclim-freetype2, and the error is related to freetype2 library
13:50:15oleoi basically am dumping the image while ignoring the master
15:42:41oleohttp://dpaste.com/22F1R3C http://dpaste.com/1QRCND6, i did a backtrace for the last one but have still no clue what's wrong
15:45:16pjboleo: typing v on the line 0: in the backtrace should jump to the source line, and you should see where the library value comes from. It's probably the variable that's bad, according to the error message.
15:46:09pjboleo: IIRC, typing RET on that line should show the frame with the bindings too.
15:47:37beacholeo: Do you have the right values for your OPTIMIZE qualities?
15:54:15oleobeach: no idea beach, do you think it's related to that ?