IRC channel logs


back to list of logs

<cwebber>propagator model stuff wip
<lilyp>heh, prolog programming in scheme
<wingo>you know, guile should de-duplicate its stack maps. should shave quite some space from binaries
<wingo>ah it's the arities that take a lot of space and have a lot of duplication. hum
<wingo>heya stis :)
<cwebber>moin moin
<lilyp>cwebber: submitted a pull request
<cwebber>lilyp: I just saw!
<cwebber>it looks good
<cwebber>I'll merge shortly
<cwebber>thanx :D
<cwebber>lilyp: consider /join #spritely btw :)
<mwette>wingo: I'm noticing that for a small function I get these arity locals: level 0: and level 2:
<mwette>by the way: i'm playing with the debug info and can't seem to get my hands on a dwarf die for my function. ANy pointers?
<wingo>yeah that's possible, depends on how much explosion in number of instructions on the tree-il->cps stage
<wingo>objdump --dwarf=info stage2/system/vm/assembler.go
<mwette>I was using (ctx-die (elf->dwarf-ctx (debug-context-elf (... foo2)...)
<mwette>I'm trying to get my hands around the debug environment, digging into system/vm/*.scm and system/repl/debug.scm and etc
<mwette>reading through dwarf-2 spec (and a tutorial doc I found)
<wingo>ah :)
<wingo>i think you want (find-program-die (program-code f))
<mwette>got it! thanks
<vijaymarupudi>I have a new blog post about scheme-bytestructures for Guile out, happy for any feedback or comments:
***robin_ is now known as robin
***manumanu_ is now known as manumanumanu
<pinoaffe>vijaymarupudi: that looks really nice, I'll definitely check out bytestructures next time I need to process binary data
<vijaymarupudi>pinoaffe: :)