Search
19:38:04
Shinmera
Even if it did it would not reflect the initial class' changes
19:38:24
Shinmera
Since the class description basically defines a bunch of initargs and initialisation functions for those sub objects
19:42:12
Shinmera
I could have a back-link from the sub-objects, but I wouldn't know when to check those, and I'd avoid having to check all the time.
19:48:24
Shinmera
Again, if I could just traverse all objects in some way to touch those I need I'd be fine. This is #sbcl, not #lisp after all.
19:53:36
stassats
karlosz: ir1 transforms
19:55:27
stassats
Shinmera: well... you can't
20:21:50
karlosz
stassats: ah thanks. i was accidentally changing the combination kinds of transforms to :local
20:54:04
karlosz
aand death in cold init
20:55:00
karlosz
but late enough where join-components gets a type error
20:55:22
karlosz
so must not be a miscompile, but rather hitting an issue on compiling a warm only thing
20:56:13
stassats
i usually conditionalize out a change, compile, then turn it on when running tests
20:56:44
stassats
(and sometimes nothing fails...)
21:17:30
stassats
maybe the stack should be divided into two portions, the second one used for passing and returning values
21:18:13
stassats
the main source of copying comes from the things like ocfp/return-pc being intermixed with the values
21:18:29
stassats
and dynamic-extent values, requiring the whole stack-analyze thing
21:20:16
stassats
the location can be stored in the thread register, kept in a wired register around calls/returns