freenode/#sbcl - IRC Chatlog
Search
14:21:31
corci
Project sbcl-master-windows » Windows_7_32bit build #2465: FAILURE in 11 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_32bit/2465/
14:23:16
corci
Project sbcl-master-windows » Windows_7_64bit build #2465: FAILURE in 13 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_64bit/2465/
15:01:41
corci
Project sbcl-master-windows » Windows_7_64bit build #2466: FIXED in 38 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_64bit/2466/
15:36:22
corci
Project sbcl-master-windows » Windows_7_32bit build #2467: FIXED in 31 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_32bit/2467/
17:02:36
slyrus_
well, I'm trying to debug/clean up some of my old code that some other old code depends on... any suggestions on how to figure out why I get note about not being able to stack allocate certain variables?
17:04:14
slyrus_
startr and friends here: https://github.com/slyrus/clem/blob/fbe5a98be7cc980b0153621be3f6e1bf646bc16d/src/defmatrix.lisp#L72
17:05:17
slyrus_
if I remove the with-map-range form everything's fine, but something in it is making it such that startr, etc... can't be stack allocated.
17:23:35
phoe
The only suspicious thing that I can see is (DECLARE (SB-PCL::%PARAMETER STARTC)) but it's suspicious because I do not know what it means.
17:24:45
slyrus_
Ok. I added in a bunch of declare dynamic-extent forms hoping to fix the problem, but sprinkling them around didn't seem to fix the problem.
17:41:51
slyrus_
ok, the relevant bits are in the gist now. I can keep going and macroexpanding, but I thought it might be helpful to see at this point first.
17:42:49
phoe
try compiling this macroexpanded code and tell me where exactly slime highlights the code when it emits the warning.
17:46:00
phoe
the vars bound in DO are I and J, whereas the warnings are about STARTC, STARTR and such
17:47:50
phoe
huh, let's try it, because why not - if you try compiling the completely macroexpanded code, where are the warnings located?
17:52:50
phoe
okay, the smallest test case I've found that seems to trigger this is (defun foo (startr endr) (do ((i startr (1+ i))) ((> i endr)) (declare (dynamic-extent i) (fixnum i))))
18:10:59
phoe
in the FOO function, the current error is that it could not stack allocate #:G9 or something
18:11:20
phoe
but if I put (declare (fixnum startr endr)) in there, suddenly the warning turns into "could not stack-allocate STARTR"
18:17:37
slyrus_
using loop gives no errors and smaller code. see the example at the bottom of the gist.
18:23:17
phoe
also http://www.sbcl.org/manual/#Dynamic_002dextent-allocation does not show any support for stack-allocating numbers, so that warning might actually be legitimate
18:26:25
slyrus_
so which is it? it's stack-allocated or not :) removing the dynamic-extent declaration makes the warning go away.
18:29:20
slyrus_
hmm... looks like I must have discovered this once before as I have a #-sbcl before the dynamic-extent declaration in another macro a few lines down.
18:57:23
phoe
my instinct is that SBCL does not want to D-X numbers because fixnums can blow up into bignums which require consing at runtime
19:00:19
corci
Project sbcl-master-windows » Windows_7_32bit build #2468: FAILURE in 20 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_32bit/2468/
19:35:41
corci
Project sbcl-cross-build-master » sparc,ubuntu_xenial_64bit build #384: FAILURE in 1 min 52 sec: http://ci.cor-lab.de/job/sbcl-cross-build-master/architecture=sparc,label=ubuntu_xenial_64bit/384/
19:35:48
corci
Project sbcl-cross-build-master » ppc,ubuntu_xenial_64bit build #384: FAILURE in 1 min 58 sec: http://ci.cor-lab.de/job/sbcl-cross-build-master/architecture=ppc,label=ubuntu_xenial_64bit/384/
19:37:20
corci
Project sbcl-cross-build-master » arm,ubuntu_xenial_64bit build #384: FAILURE in 3 min 30 sec: http://ci.cor-lab.de/job/sbcl-cross-build-master/architecture=arm,label=ubuntu_xenial_64bit/384/
19:37:26
corci
Project sbcl-cross-build-master » arm64,ubuntu_xenial_64bit build #384: FAILURE in 3 min 36 sec: http://ci.cor-lab.de/job/sbcl-cross-build-master/architecture=arm64,label=ubuntu_xenial_64bit/384/
19:38:21
corci
Project sbcl-cross-build-master » alpha,ubuntu_xenial_64bit build #384: FAILURE in 4 min 31 sec: http://ci.cor-lab.de/job/sbcl-cross-build-master/architecture=alpha,label=ubuntu_xenial_64bit/384/
19:38:45
corci
Project sbcl-cross-build-master » hppa,ubuntu_xenial_64bit build #384: FAILURE in 4 min 55 sec: http://ci.cor-lab.de/job/sbcl-cross-build-master/architecture=hppa,label=ubuntu_xenial_64bit/384/
19:38:47
corci
Project sbcl-cross-build-master » mips,ubuntu_xenial_64bit build #384: FAILURE in 4 min 57 sec: http://ci.cor-lab.de/job/sbcl-cross-build-master/architecture=mips,label=ubuntu_xenial_64bit/384/
19:49:50
corci
Project sbcl-master-windows » Windows_7_32bit build #2469: FIXED in 28 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_32bit/2469/
20:55:16
corci
Project sbcl-master » default,MAC_OS_mavericks_64bit build #3278: FAILURE in 11 min: http://ci.cor-lab.de/job/sbcl-master/featureset=default,label=MAC_OS_mavericks_64bit/3278/