Search
Thursday, 23rd of August 2018, 19:34:54 UTC
19:35:08
kpoeck
(type-of (+ most-positive-long-float most-positive-long-float) ) -> double-float
19:38:42
kpoeck
Now I see (si::trap-fpe 'last nil) in the codebase
19:39:45
Shinmera
Afaiu you need to instruct the CPU's FPU which things should cause exceptions, so some things might also just not be enabled.
19:41:26
kpoeck
Unfortunately my buddy UNDEFINED-FUNCTION (:NAME INLINED-TWO-ARG-/) failed, so I have to recompile all cclasp
19:43:47
kpoeck
and waf now compiles nearly everything from scratch, this build system needs some tender care
20:48:52
kpoeck
(+ most-positive-long-float most-positive-long-float) -> #.ext:double-float-positive-infinity
20:51:09
kpoeck
but this is just the printing
20:52:17
kpoeck
(ext:float-infinity-p (+ most-positive-long-float most-positive-long-float)) -> t
20:54:40
Shinmera
Right, so it ignores/masks the overflow exception
21:08:38
kpoeck
Just don't know how to set that off
21:10:45
Bike_
a float death? use doubles
21:11:26
Shinmera
You need to instruct the FPU to cause an exception.
21:12:50
Shinmera
ECL has the si::trap-fpe function that allows you to do that.
21:12:58
Shinmera
https://github.com/Shinmera/float-features/blob/master/float-features.lisp#L175
21:25:58
kpoeck
Yes, but there don't seem to be a si::trap-fpe in clasp
21:27:33
Shinmera
Then it needs to be added, most likely :)
21:28:19
kpoeck
In line 193 of float-features.lisp, with #-(or abcl ccl clisp cmucl ecl sbcl) don't you need to add clasp?
21:29:03
kpoeck
as in #-(or abcl ccl clasp clisp cmucl ecl sbcl)
21:30:24
Shinmera
No, since clasp does not support with-float-traps-masked yet
21:50:28
kpoeck
@Shinmera, see pr https://github.com/clasp-developers/clasp/pull/585
22:41:58
makomo
now there's a second CLASP: https://www.radioeng.cz/fulltexts/2011/11_04_880_889.pdf :-)
22:42:22
makomo
"now" being 2011 i guess :D
22:47:45
stassats
with FUNCTION and QUOTE
22:47:56
Shinmera
And the classic LISP capitalisation
2:32:50
davidlovemore
drmeister: What is the issue with simple-vector?
3:52:23
beach
Good morning everyone!
3:52:48
beach
Bike: 11 times sounds bad.
4:06:25
beach
Source tracking pretty much works in SICL now.
4:06:52
beach
When I translate HIR to Common Lisp, I include the source information.
4:07:30
beach
So when there is an error, there is a variable in the stack frame that contains the source information. By using RET in SLIME I can then inspect the source information.
4:07:57
beach
It is not extremely convenient yet because I am still doing this inside SBCL.
4:17:10
beach
But the source information contains the line and column number of the beginning and the end of the expression being evaluated, and it contains the full text of the code that produced it. So by using the SLIME inspector, I can immediately see what expression is being evaluated.
Friday, 24th of August 2018, 7:34:54 UTC