1.0.30.44: DECODE-FLOAT and INTEGER-DECODE-FOAT are not flushable
authorNikodemus Siivola <nikodemus@random-state.net>
Wed, 12 Aug 2009 11:14:15 +0000 (11:14 +0000)
committerNikodemus Siivola <nikodemus@random-state.net>
Wed, 12 Aug 2009 11:14:15 +0000 (11:14 +0000)
commitd9824d93818d7b212acd2bfda2c5fe0fd150c093
treedf7082743730c75462fe829a8398f8c4a19379e5
parent8e73cf67d15bf0aeed37ac38d309aa9048b29573
1.0.30.44: DECODE-FLOAT and INTEGER-DECODE-FOAT are not flushable

 ...as they should signal an error for non-floats in safe code,
 and hence UNSAFELY-FLUSHABLE.

 Ditto for FLOAT-SIGN, FLOAT-RADIX, FLOAT-DIGITS, and FLOAT-PRECISION,
 though for some reason Python seemed unwilling to delete these calls
 despite them being marked as flushable as well.

 See: https://bugs.launchpad.net/sbcl/+bug/412416
NEWS
src/compiler/fndb.lisp
tests/compiler.pure.lisp
version.lisp-expr