freenode/#sbcl - IRC Chatlog
Search
12:26:41
|3b|
does sbcl change FP settings beyond traps? (on x86_64 in particular), and if so is there some way to set them back to whatever C would expect during a FFI call?
14:01:44
flip214
Ie. if I use, say, 1.4.4 on Debian and on CentOS, will the FASLs be different, or can they be shared (eg NFS mount)?
14:02:46
flip214
I guess a difference could be absolute paths of libraries.... but OTOH most will just load "libssl.so.10" etc., and LD will do the rest...
16:03:58
stylewarning
flip214: FASLs can’t even be trusted on the same OS with a minor change in version
17:04:36
scymtym
dougk__: the sb-sprof breakage is likely due to my changes. i will have a look once child is in bed
17:33:01
stassats
|3b|: changing FPU modes is expensive, you need to perform it manually if you wish
17:43:06
|3b|
stassats: yeah, was trying to determine if it was wished (trying to help debug some ffi to foreign lib that gets different answers when called from sbcl or from c)
19:42:13
flip214
ouch. (SXHASH `((:key1 "string1") (:key2 "string2") . X)) collides even for different X'es. That's unexpected.
20:11:59
stassats
(SXHASH `((:key1 "string1") (:key2 "string2") . X)) and (SXHASH `((:key1 "string1") (:key2 "string2") . Y))
20:15:05
pfdietz
sxhash is more optimized for speed; not to be a crypto hash that depends on everything.
20:17:10
flip214
in the pastebin you can put comment markers on the lines beginning with %r14 and get the same result
20:21:47
flip214
stassats: because I don't care about the operands themselves - I don't even split them up.
20:22:57
flip214
no, I need to reproduce them later on. but isn't that completely tangential to the SXHASH collisions?
20:36:42
flip214
well, generating a text string via (format nil "~(~36,12,'0r~)" (SXHASH input)) was really convenient...
20:40:07
flip214
yeah, the function now pre-allocates a string, and writes character by character into it. could be done much shorter, I guess.