libera/#clasp - IRC Chatlog
Search
14:17:06
yitzi
drmeister: I could use your help when you have time. I am trying to setup a "non-clbind" version of lila, but I am getting some errors. I don't think I have the "project_headers" stuff defined correctly.
14:43:51
Bike
::notify karlosz it might be slightly more convenient if jumps were relative to the most significant (last) byte of the label rather than the least
14:44:53
Bike
::notify karlosz having the mv-call instructions handle value popping themselves might be better- as is I think I'll need to copy the mvalues into a VLA so the callee doesn't need to worry about them getting stomped
14:49:05
Bike
without copying i guess there'd be a little memory leak in that the callee would still be on the stack during the call, but it's going to be alive anyway given that it's running, so it's just a wasted stack slot
16:35:39
Bike
drmeister: i think the entry-point-as-function thing is a little broken - trying to get the function name of an entry point segfaults
16:36:00
Bike
drmeister: i don't quite follow why, if you did the self pointer thing, since it should go entry-point -> entry-point -> function description -> name
16:56:49
yitzi
I think that clbind's `def` might actually already be equivalent to CL_DEFMETHOD...just subtly broken.
17:20:15
Colleen
karlosz: Bike said 2 hours, 36 minutes ago: it might be slightly more convenient if jumps were relative to the most significant (last) byte of the label rather than the least
17:20:15
Colleen
karlosz: Bike said 2 hours, 35 minutes ago: having the mv-call instructions handle value popping themselves might be better- as is I think I'll need to copy the mvalues into a VLA so the callee doesn't need to worry about them getting stomped
17:23:13
karlosz
also: re: labels: i can change it to msb if its more convenient. i'm working on short jump encoding "compression" (really "expansion" since i'll try to do it optimistically since that gives better code) because i have a good handle on how to do it i think
17:25:20
karlosz_
Bike: re: mv-call. i remember thinking about this issue and there was some reaosn why its the way it is... maybe something about optimizing for mv-call with 1 arg value being faster that way?
17:25:44
karlosz_
im thinking (FDEFINITION n) (CALL) (MV-CALL) is more optimized that way if you had mv-call not do popping
17:27:19
Bike
because the callee might call some other function and then try to grab some of its own arguments, but that other function will have stomped the mv vector
17:28:30
Bike
that's true about fdefinition call mv-call though... i guess in that case there kind of needs to be a copy
17:32:07
Bike
okay, now that i have straightened out the disassembler it looks like the label for jump-if-supplied is not getting linked. probably it should not be zero
17:34:30
Bike
oh, wait, emit-jump-if-supplied just puts in zeroes instead of giving ASSEMBLE the label