freenode/#clasp - IRC Chatlog
Search
13:43:42
Shinmera
This one, to be specific, since there seems to be a another one. http://www.mr511.de/software/english.html
13:45:18
Shinmera
Actually not sure if that's the same one as what's included in https://sourceware.org/elfutils/
15:25:20
pfdietz
Also the whole solve the problem of aging thing was one of the stronger hooks I've seen in a lisp talk.
15:30:48
Bike
drmeister: so if you look at one of the weird empty frames for print-object you'll see that the stream is actually a file-stream for /dev/null. As it happens, when you print with circularity, everything actually prints twice- one "dry run" to /dev/null probably to get all the #n# right, before the actual one.
15:30:48
Colleen
Bike: frgo said 2 hours, 30 minutes ago: See https://github.com/clasp-developers/clasp/issues/638 : BUG: Input #<LEXICAL-LOCATION G15563251> not previously defined
15:31:34
Bike
drmeister: and the error from print-unreadable-object is apparently signaled during this first dry run print.
15:32:11
Bike
drmeister: that's half the problem. now i think the display weirdness is because sldb is trying to print the objects to /dev/null instead of where it should actually be going. i dug around but couldn't work out why it would be doing that, or if it actually is.
15:56:00
drmeister
Dammit - in the talk I said it takes half-an-hour to build clasp. I was wrong about that - it's about 50min right now.
17:44:50
shiho
drmeister: My build is stuck in "Loading/compiling source: /Users/shiho/Development/cando/src/lisp/kernel/cmp/cmprepl.lsp" again.
23:11:22
drmeister
Bike: The thing with printing clos objects - we expect the following to fail - right?
23:14:59
scymtym
drmeister: what are you using for the interactive exploration of flamegraphs you mentioned?
23:16:30
drmeister
It's the best svg viewer that I have - but it bogs down for large flamegraphs that we get if we aren't extremely careful profiling cleavir.
23:17:34
scymtym
maybe i can make a backend for the clim-based flamegraph thing once clasp runs mcclim
23:24:49
drmeister
That would be useful - but I've been thinking of hacking the flamegraph stuff to reduce the complexity of the flamegraph - to remove the "sparks".
23:25:20
drmeister
Hey - we got the SMARTS stuff to work pretty well - the chain and branch code is working now.
23:25:54
drmeister
I asked shiho to do some more validation with example smarts strings and check if the generated objects look correct.
23:30:56
scymtym
let me know if you need changes in the parser itself - or you can take over the project, if you want to
23:46:05
drmeister
Say I have a function call (foo a b c d e f) what if I passed the arguments call foo (a b c d a b c d e f)
23:47:47
drmeister
That would pass the arguments in registers, and spill the arguments onto the stack. I spill anyway - so this wouldn't add any runtime cost that I am not already paying.
0:30:01
Bike
drmeister: yes, if you print an object with no special print-object it goes through the default method, which tries to use #<> syntax, which signals an error if *print-readably*