freenode/#clasp - IRC Chatlog
Search
21:05:38
kpoeck
Better reference w/o errors: https://common-lisp.net/project/cl-test-grid/library/array-utils.html
21:28:57
Bike
so clasp's sequence functions work with "iterators" that are kind of like the sequence extension's. i found that if we go a little farther with that and have make-seq-iterator return "pre-dispatched" functions to work with them, iteration functions go twice as fast ish
21:32:29
Bike
of course going to a specialized version based on type inference would still be better
0:13:55
Bike
i had another thought - we might be able to reorganize loading clos to be less side effect oriented. we can just make method and generic function objects directly (i.e. not through make-instance) and set up a discriminating function that's not through the usual method but still perfectly good
0:27:04
drmeister
Bike. Lang came back with a response that I forwarded to you. Could you come up with an ld64 patch?
0:29:03
Bike
i don't know whether i can just write in another N_OSO stab or what, and i can't imagine they'll accept a patch to a core system program based on just any dumb experiments i do
0:32:23
Bike
i was hoping we could get in touch with someone who understands the linker and mach-o and stuff, so they could give us some guidance, or just fix it themselves
0:58:15
Bike
if you want me to take some time to understand ld64 i can try, but i really doubt i'll be able to do anything very quickly
1:32:03
drmeister
I talked with Martin about this. He thinks it would be good to give them something that illustrates the problem if we could. They’d certainly rewrite it.
1:33:16
drmeister
Then compile it three times with different defines that turn on one part at a time.
1:35:52
drmeister
With a demo and a patch that fixed the demo they’d get on it quick. That’s Martins assessment.
1:39:59
karlosz
kpoeck: interesting. good to hear it cross compiled at some point - i'm interested in comparing the performance of the self build
1:40:54
karlosz
i find that cross compiling sbcl is a nice benchmark because numeric performance is usually not a factor, so but rather being able to elide type checks and optimize structs well
1:42:08
karlosz
host-1 would be a test of the compiler's speed and host-2 a test of generated code speed