freenode/#clasp - IRC Chatlog
Search
12:19:58
kpoeck
drmeister I am about the integrate the regression-tests in waf as `./waf regression_tests`
12:21:28
drmeister
For now I think you would have to. Unless you can figure out how to require waf to build it if it isn't there.
12:21:37
kpoeck
i think it is no longer created for `USE_COMPILE_FILE_PARALLEL=False`I 'd fix that too
12:22:13
Bike
can we like, always make it? like even if there's whatever obscure linking thing, make a shell script instead of an executable there
12:22:53
kpoeck
After every build i do "ln -s -f ~/lisp/compiler/clasp-karsten/build/boehm/cclasp-boehm ~/lisp/compiler/clasp-karsten/build/clasp"
12:28:35
kpoeck
I also looked at signal-handling and sigfpe, please have a look on https://github.com/clasp-developers/clasp/pull/955
12:36:04
kpoeck
#if !defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE)#define FPE_NOOP 0 /* if only I knew... */#endif
12:37:01
Bike
oh, why did you turn off init_float_traps()? when i did t hat before i hit problems when i did more than one FPU error, i think
12:37:12
Bike
of course, if you can't recover from an FPU error to begin with, i guess it doesn't matter
12:43:40
Bike
mm, well if it's a no-op anyway having it there is fairly harmless, and it might eventually not be a no-op. but we can probably just leave it out until we get more of a handle on things, by which i mean fixing the out of extent return
12:49:09
kpoeck
drmeister in https://github.com/clasp-developers/clasp/blob/dev/wscript#L1566-#L1574 . don't you symlink twice?
14:06:23
kpoeck
anyhow defined `./waf regression_tests` in https://github.com/clasp-developers/clasp/pull/960
16:36:53
Bike
hi. doing function name stuff. might be able to eliminate clasp's named-function-ast and stuff. then since i'm already elbow deep in cleavir i could see about marking variables as something we should care about for debugging, but i'm not sure of the particulars there
17:39:12
kpoeck
jackdaniel regarding floating point errors and platforms where FEENABLEEXCEPT is not available. Do I understand correctly that ecl uses ECL_MATHERR_TEST after every calculation that could give a floating point exception?