10:25:25_deathit's very cool to see sb-simd as a contrib.. compiled new sbcl today and no problems so far
17:56:07stassatsflip214: avx has nothing to do with fasls
17:57:34stassatsthe comments around bignum-truncate are quite wrong...
17:58:56stassatsso are they wrong and it's ok, or is the code wrong
18:28:58flip214stassats: so I can build sb-simd on a non-avx machine and use compiled libraries on an avx machine, with speedup? And the other way around as well?
18:30:00stassatsnot sure if just during constant folding
18:32:14|3b|presumably simd code would do a runtime check and not call the avx versions of functions if they won't work
18:32:58stassatsthat happens with the avx2 routines that coincidentally are in this release, but not related to sb-simd
18:33:51|3b|ACTION hopes the ability to do that stuff ended up in the final thing, since that was one of my requirements. requiring it to build is more or less OK, but need to be able to make binaries that run anywhere (even if that needs some coding to enable)
18:34:24stassatsdon't know about sb-simd and multi-versioned functions
18:35:14_deathI think the sb-simd docs mentions this
18:35:33stassatsin normal sbcl: #'sb-vm::simd-nreverse8 => #<FUNCTION SB-VM::SIMD-NREVERSE8-AVX2>, gets redefined at startup