freenode/#sbcl - IRC Chatlog
Search
15:06:03
scymtym
interesting effect on default and fancy core sizes of the "x86-64: Factor out and adjust double-wide CAS emitter" commit: https://ci.cor-lab.org/job/sbcl-master/featureset=default,label=ubuntu_trusty_64bit/plot/ https://ci.cor-lab.org/job/sbcl-master/featureset=fancy,label=ubuntu_trusty_64bit/plot/
16:06:36
scymtym
stassats: sure, the x86 cores grow and shrink in smaller increments and thus usually react to changes more directly, but this particular commit only affected x86_64
16:07:27
scymtym
unfortunately the plot plugin sucks. if you look at it wrong, let alone touch the configuration, it throws away all historic data
16:09:03
scymtym
yeah, all i'm hoping for is maybe catching dramatic changes between successive builds. it is not good enough for any form of longer term monitoring
16:25:21
scymtym
is it using this https://sourceforge.net/p/sbcl/sbcl-git-hooks/ci/master/tree/post-receive-email ?
16:53:36
Xof
re sbcl-commits: it is or was using that, but it is possible that sourceforge has changed things
16:53:54
Xof
and it is definitely true that sourceforge has broken shell access, so I can't actually see what's in the hooks for the master repository
16:54:30
Xof
honestly at this rate it might be quicker to get French citizenship for my children than get all of sourceforge working again
16:58:45
scymtym
maybe we had the git config variables described in the header comment of the script in the old GIT repository and they got lost in the migration. but as Xof says, no way to know without shell access
17:00:35
scymtym
i think you have to copy it into the repository for changes to go into effect. that's what the README seems to say
17:42:45
scymtym
i would like to push these changes to sb-sprof https://github.com/scymtym/sbcl/tree/wip-sb-sprof . the changes are sufficient for supporting an initial version of the clim flamegraph thing ( https://techfak.de/~jmoringe/clamegraph2.png ). do the changes look OK?
18:52:22
stassats
i think my final plan for source location would be to hook into reader macros, by function name, when READ is called by an unknown reader macro, unwrap the form but save all conses / atoms (some might be used only once), and when that reader macro returns, rewrap anything that is still EQ
18:57:22
scymtym
the crazy alternatives would be running macros and reader macros in a special interpreter or turning ATOM, CONSP, CAR, etc. into generic functions that also work on syntax objects
18:58:23
corci
Project sbcl-master ยป without-threads,ubuntu_trusty_32bit build #3124: FIXED in 14 min: http://ci.cor-lab.de/job/sbcl-master/featureset=without-threads,label=ubuntu_trusty_32bit/3124/
18:58:47
stassats
but for macros, i had another idea, since they are defined by defmacro usually, we can instrument stuff there, no need to interpret or compile anything
18:59:10
stassats
just see if a form just goes , into a list that is returned or into a third party function