freenode/#clasp - IRC Chatlog
Search
17:49:05
kpoeck_
Selwyn, great that you have less errors with cffi trst, could you attach your results to the issue
17:50:05
kpoeck_
I believe one problem is that clasps fli take char as a character, where some tests seem to usr char like int
17:52:03
kpoeck_
Yesterday i tried compiling the top 50 quicklisp libraries in clasp, apart from ironclad that seems to work ok (just compiling, did not test)
17:53:23
kpoeck_
The parallel compiler does not seem to like empty files, e.g. when the only form is #+sbcl (progn. )
18:11:12
drmeister
We used to build ironclad - but it took a looooong time. The compile-file-parallel should have improved the compile time.
18:12:56
drmeister
Yes - right - that happened to me as well - and I've seen it crash and I associated that with the boehmgc warning.
18:13:51
kpoeck_
In https://github.com/clasp-developers/clasp/wiki/Quicklisp-libraries-in-Clasp in started documenting the mail quicklisp systems
18:14:15
selwyn
i didn't fix anything myself, i was interested to see the effect of this fix to %inc-pointer. i just realised i am not using clasp-developers/cffi on this computer - perhaps i can get even fewer errors
18:21:57
selwyn
the tracker contains results pertaining to quicklisp cffi, i will leave them unchanged. interesting that i got some failures that you did not: SHAREABLE-VECTOR.1, SHAREABLE-VECTOR.2
18:33:19
kpoeck_
Now they propose to base it on static-vectors, where drmeister is not sendig the pr whith rhe definitios for clasp
18:55:17
selwyn
it's great news that so many quicklisp libraries compile. could i have write access to the wiki? i ran a test suite for lparallel and thought i might add the results to kpoeck's new page
18:55:59
selwyn
or you can do it yourselves (ql:quickload :lparallel-test) (lparallel-test:execute) -> Success: 171 tests, 119190 checks.
19:22:06
kpoeck
drmeister: I get the following compiling ironclad: .......Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
19:22:41
kpoeck
Somewhere I read than one should do the following to avoid that: export GC_INITIAL_HEAP_SIZE=40G
19:23:55
drmeister
I think the MAXHINCR or MAX_HEAP_SECTS are compile time cpp variables - I've been using the package manager installed boehm.
19:25:59
drmeister
It would be good to know that setting an environment variable can bypass this problem with ironclad.
19:26:38
drmeister
I'm leery of pulling boehm into Clasp's build system to take more control of these settings - that sounds like a huge headache.
19:46:52
drmeister
It's interesting how close Common Lisp and C++ are in the left diagram and yet how far apart they are.
20:14:19
kpoeck
cacha.lisp is 193 lines, it compiles to 116 MB in cacha.bc, something strange going on in ironclad
21:41:42
drmeister
https://github.com/fredokun/cl-jupyter/blob/13b18ffdd688bef42e41546f4740411333a5a115/src/message.lisp#L163
21:42:29
drmeister
Back in the day we sat through that multi hour compilation of ironclad for that one bit of functionality.
21:43:03
drmeister
Then I added a hundred line C++ source file to clasp and hotwired the C++ function in - and removed the need for ironclad.
21:43:57
drmeister
Bike: copying iclasp-boehm to cando and then having the executable recognize that and add a command to load the cando lisp code works great!
22:44:25
drmeister
kpoeck: Did one of those top 50 quicklisp systems that compiled with clasp happen to be clpython?
22:55:42
drmeister
No worries - I ql:quickloaded it into sbcl and then I hacked up the #+ecl to #+(ecl clasp) where it made sense and I'm building it now.
22:59:22
drmeister
Neat! checking-reader-conditionals is a facility in clpython to recognize when an implementation doesn't provide a reader conditional.
23:01:10
drmeister
I'm messing with clpython because in a couple of weeks I'm going to talk to a bunch of people who will be very anxious about learning Common Lisp - if I optionally provide python inside of cando it may alay their anxiety.
23:20:12
scymtym
drmeister: is the goal to provide users with a familiar language for scripting or do your users expect to have their python ecosystem available in cando?
0:15:50
drmeister
Class #<The STANDARD-CLASS CLPYTHON::DICT-MIXIN> is not a valid superclass for #<The CLPYTHON::PY-META-TYPE CLPYTHON:PY-TYPE>
0:24:02
Bike
maybre it's trying to make the classes at compile time before the validate-superclass methods are installed
1:12:44
drmeister
This cannot succeed for class #<The CLPYTHON::PY-META-TYPE CLPYTHON:PY-TYPE> and superclass #<The STANDARD-CLASS CLPYTHON::DICT-MIXIN>
1:12:53
drmeister
https://github.com/clasp-developers/clasp/blob/dev/src/lisp/kernel/clos/standard.lsp#L303
1:14:58
drmeister
The class of clpython:py-type is clpython::py-meta-type and the class of clpython::dict-mixin is standard-class
1:27:10
drmeister
I see - clpython defines a closer-mop:validate-superclass - but clasp doesn't use it because it's not in the clos class.
2:55:33
drmeister
::notify Bike Tomorrow can you explain to me how closer-mop is supposed to work with the existing clos? clpython defines several closer-mop:validate-superclass but they won't be called by the clasp clos code.
2:58:25
drmeister
::notify Bike Also, I tried to remove quicklisp from the cando startup but it's needed to resolve dependencies for some of the systems. I also need quicklisp to build the systems the first time cando is run. Is there a way around this? If not - we have to keep loading quicklisp at startup.
4:11:56
drmeister
::notify Bike - I think I uncovered a subtle problem with clasp's generic function dispatch when building clpython.