freenode/#clasp - IRC Chatlog
Search
19:53:23
cracauer
I can confirm that the excessive memory usage I had in quicklisp went back to normal without compile-file-parallel
20:29:53
kpoeck
I had the problem that (cmp:compile-file-parallel "sys:regression-tests;framework.lisp") did not work, probably because core:write-faso did not work with logical pathnames
20:30:55
kpoeck
The other problem is that bot compile-file-serial and compile-file-parallel do not respect the extension, when a output-file is given
20:31:40
kpoeck
(cmp:compile-file-parallel "sys:regression-tests;framework.lisp" :output-file "sys:regression-tests;framework.tmp-fsl" :verbose nil :print nil) -> #P"SYS:REGRESSION-TESTS;FRAMEWORK.FASP.NEWEST"
20:32:24
kpoeck
This break sbcls crosscompiling that expects a file with extension "tmp-fsl" is produced
20:33:01
kpoeck
(cmp:compile-file-serial "sys:regression-tests;framework.lisp" :output-file "sys:regression-tests;framework.tmp-fsl" :verbose nil :print nil) does the same
20:34:32
kpoeck
I understand that a "tmp-fsl" file cannot be loaded, but sbcl renames the extension before loading it, so that works fine
20:36:57
kpoeck
and cmp::output-cfp-result seems to be calling uselessly (compile-file-pathname output-path :output-type output-type) again on an output-path that already is fully calculated
21:25:47
drmeister
cracauer: that’s interesting that the memory usage went down. That means it’s not the faso files/object files in memory that is the problem. It’s something about the multithreaded compilation.
22:08:27
kpoeck
oops, (cmp:compile-file-parallel "sys:regression-tests;framework.lisp") does not work, leaves the fasl in the root directory
22:52:48
drmeister
This fails ... (load (cmp:compile-file-parallel "sys:regression-tests;framework.lisp"))
22:53:41
drmeister
kpoeck: Are you online? Could you tell me exactly what problem you are running into?
23:09:30
drmeister
Ok - there is a serious problem that pr #918 addresses - but I'd like to change how these problems are fixed.
23:10:36
drmeister
https://github.com/clasp-developers/clasp/pull/918/files#diff-d58dcfefc359837b354c57824070cb13R351
23:11:35
drmeister
Shouldn't we move the translate-logical-pathname into write-faso - so that it takes logical pathnames.
23:19:56
drmeister
It first coerces the argument to a pathname and then if its a physical pathname it is returned. That's benign - isn't it?
23:20:39
drmeister
kpoeck's solution if a good one - but I don't want write-faso to catch me in the future so I'll move the call into write-faso.
2:24:51
drmeister
There is a recent update to piou - it indicates that it may be working with the latest ASDF.
3:01:11
Bike
it doesn't like something in https://github.com/melisgl/named-readtables/blob/master/src/cruft.lisp
3:04:43
Bike
https://github.com/clasp-developers/clasp/blob/dev/src/lisp/kernel/cleavir/toplevel.lisp#L123-L129 yeah, i wrote this wrong
3:05:18
Bike
uhh, test by doing (clasp-cleavir::simple-eval-cst (cst:cst-from-expression '(progn)) nil (lambda (&rest ignore)))?
3:08:16
Bike
(loop with result = nil for cstl = list-cst then (cst:rest cstl) do (setf result (recurse (cst:first cstl) env)) finally (return result))
4:01:53
Bike
yeah. also you can test it without rebuilding using something like the cst-from-expression form i did earlier.