freenode/#clasp - IRC Chatlog
Search
13:37:06
Bike
the majority of remaining origin-less instructions seems to be compile-form (i.e. load time value). for those that are in the actual loader we don't really care i think, but we also end up using load-time-value for typeq... t hat might be funnier to deal with
15:20:24
Bike
couple place in inlining, in segregate lexicals... and internal array instructions for some reason, gotta figure that one out
17:56:21
Bike
ok got no-source-info instructions from ppcre down to load time values, top level enters and their returns, and two assignments which i don't know what's going on with them
18:23:50
kpoeck
Being april first, i made a pr to support Shinmera s float-features with https://github.com/clasp-developers/clasp/pull/962
19:10:36
kpoeck
I did not dare to activate that globally, since clasp in to many places throws sigfpe
19:11:40
kpoeck
e.g (flet ((foo () (if (> 10 (random 20)) 0.0 0.0)) (bar () (if (> 10 (random 20)) 23 24))) (ext:with-float-traps-masked () (/ (bar) (foo)) ))
19:13:37
kpoeck
Did 8 test-cases for float-features with parachute and tested them with clasp, sbcl and ccl
20:15:38
Bike
let's seee... the test-char are the char comparisons... some loop problems... are all the number comparison ones similar to the char comparison problems?
20:20:55
kpoeck
I reported one of these errors for ecl and he fixed it (and I backported it to clasp)
20:23:33
kpoeck
ecl warns nicely that : ;;; Warning: The form #C(0 1) evaluated to #C(0 1), which was not of the anticipated type REAL.
20:28:16
kpoeck
Thats why I believe that the loop macro generates wrong code (and clasp complains correctly)