freenode/#clasp - IRC Chatlog
Search
13:03:58
drmeister
Bicyclidine: We rewrote layout-procedure and now the shadow stack isn't being constructed.
13:07:24
drmeister
cracauer: You asked about backtrace.lisp:107 earlier - what statement are you referring to?
13:07:48
drmeister
https://github.com/clasp-developers/clasp/blob/dev/src/lisp/kernel/lsp/backtrace.lsp#L106
13:21:20
Bike
bclasp and sldb aren't getting along now, and it doesn't know how to require asdf even though i already built it. did i justbreak everything
13:35:24
drmeister
I love this jupyterlab interface - if I could just get it to indent code the way emacs does it would be glorious.
13:37:12
Bike
"Could not load bitcode for file bla bla bla asdf.ll - error: expected top-level entity"
14:04:24
Bike
how do i get the "Could not load bitcode" error? Trying to load cleavir in the workbench
14:05:35
drmeister
Urgh! I think these are still teething issues with adding the 'object' build mode. The workbench code probably needs to be tweaked to work with it.
14:34:07
davidlovemore
Parallel builds with MPS now work for me. I have created pull request: https://github.com/clasp-developers/clasp/pull/530
14:53:42
balrog
davidlovemore: nice! I'm still wondering just why you need that cfg.env["DEST_OS"] hack, though......
15:01:47
davidlovemore
balrog: I guess it is not logically part of change. But update_whatever_it_was uses DEST_OS before it is set otherwise. The change means I don't need to make a wscript.config file with DEST_OS set explicitly which was a workaround.
15:05:34
davidlovemore
drmeister: In terms of priorities what would you like us to work on next? I am just starting to think about gc'able LLVM code.
15:20:16
beach
attila_lendvai: I need to convince myself whether NIL is acceptable as a global environment (it would be a designator). I think it is, in which case the documentation should be modified.
15:24:16
attila_lendvai
beach: I prefer things to be explicit so that the intention is clearly encoded, and e.g. accidental NIL's are caught early (as opposed to silently misbehaving code relative to the coder's intentions), especially when it's not an API that is used pervasively throughout the codebase. so, I'd argue against that.
15:25:13
beach
Sure, I understand. I just need to verify that we have a class for all global environments, and that Clasp won't break if we don't. Stuff like that.
15:25:16
attila_lendvai
beach: IOW, DWIM stuff only in API's that are used a lot and as such are clear part of the coder's internal mental model
15:44:27
Bike
drmeister: I think if you just defined the compute-policy-quality method for maintain shadow stack to always return T (through a reader conditional, i guess) you'd get what you want. It's on L41 of policy.lisp.
16:46:23
Bike
i don't think i actually told you: when it hits boot.lsp in clos, it says +builtin-classes-list+ is unbound.
16:47:39
drmeister
core:+builtin-classes-list+ is bound in the C++ interpreter - does it have a value?
16:49:53
drmeister
I was thinking of core::*all-cxx-classes* <--- that is set up in the interpreter.
16:51:42
drmeister
https://github.com/clasp-developers/clasp/blob/dev/src/lisp/kernel/clos/hierarchy.lsp#L195
16:52:37
drmeister
ECL gets away with only defining these hierarchy.lsp global variables at :compile-toplevel and :execute time.
16:52:59
Bike
but this is in the bclasp+cleavir building cleavir stage, so i think it just needs to be bound at compile time for this
16:55:30
kpoeck
Bike: could you have a look at pr 519, much more regression tests, so i hope not controversial
18:07:06
drmeister
kpoeck: Hi - I couldn't reproduce the crash that you saw - did the problem go away?
18:41:11
Bike
ok so the problem _might_ be that it's hitting a #., and the *package* isn't set to read it right... i'm really not sure
18:52:22
Bike
drmeister: also- the function-info contains a docstring, right? I tried it out and i can't seem to retrieve it. is that something else the merge broke?
18:53:00
drmeister
The function-info contains an integer index into the root vector for the module that contains a docstring.
18:55:02
attila_lendvai
Bike: would you like ./waf -f some-feature to work so that ./waf configure stores it, and subsequent waf invocations will use the value stored at configure?
18:57:30
attila_lendvai
hrm... it seems useful when people experiment with stuff, though. but I'm not sure with what semantics I should add. drmeister, any opinion on this? forget it for now? or add as a direct copy of ./waf -f foo to clasp -f foo, i.e. not have ./waf configure store it?
18:58:42
Bike
if i wanted to store it in the configuration i think i'd rather just write it in the configuration myself
19:01:24
attila_lendvai
my idea is that you add something to the codebase that slows things down, but enables better debugging. then sometimes you start a build by ./waf configure --feature heavy-debugging-stuff and until the next ./waf distclean all clasp invocations will have that feature
19:02:46
attila_lendvai
./waf -f debug already does this (it enables 4 features), except that it's not stored in the configure phase
20:25:11
Bike
if i turn inlining on and uncomment inline.lisp it dies silently, but it's going okay without that (so only inlining lets and local functions i guess)
20:31:05
drmeister
Could it be that the criteria for inlining functions is incorrect? Beach said this was something we needed to be very careful of.
20:36:46
Bike
it dies silently when bclasp+cleavir gets toinline.lisp, i.e. when it's actually using the compiler for the first time
21:21:13
attila_lendvai
ACTION is back at playing with his staged-bootstrapping idea, stripping down stage-1 to contain only what's need for iclasp
21:25:39
attila_lendvai
I may be missing something, but it makes a whole lot more sense to me to have separate codebases managed by the VCS for the separate bootstrap stages. similar-looking, cherry-picking commits, yet free to diverge when needed. we'll see how much of the complexity I'm not aware of and how much it will bite me on the way, though...
21:32:07
attila_lendvai
Bike: I'm hoping that git cherry-pick can help manage that. and I also hope that it will happen fewer and fewer times when stage-n-1 needs to be touched to build stage-n. keep in mind that it will be easy to "escape forward" and introduce a new stage for a new feature. some stages can even continue building using an ancient version of cleavir...
21:33:18
drmeister
I did a full build this morning - on ubuntu - there was no problem. That's why I'm perplexed.
21:34:32
karlosz
ill just do cleavir-mir: for now but it seems like thats just like any other hir modification