Search
Wednesday, 20th of September 2017, 18:00:44 UTC
18:32:05
Bike
fixed the build thing, onto arrays...
18:43:53
drmeister
Bike. Is it still necessary to code walk to determine call-next-method and next-method-p in cleavir?
18:44:28
Bike
you mean whether they're used?
18:45:16
Bike
also, i can't reproduce the array thing. i thought it was just that negative numbers didn't work right in signed-byte arrays
18:45:18
drmeister
Clasp does this when compiling methods. Beach always said it would be unnecessary at some point in cleavirs development.
18:46:17
Bike
I'm missing context here. Why is this done?
18:46:23
Bike
Just to avoid binding call-next-method if it's not used?
18:47:00
Bike
assuming that "this" does mean determining whether a method body does use them
18:47:20
Bike
i think cleavir will still cons up a closure for unused functions
18:48:06
drmeister
I think beach meant unused closures would be discarded
18:48:58
Bike
right. i don't think that's done yet. i could probably whip up a "delete instructions whose outputs aren't used" phase though. might be a little weird with side effects
19:07:00
Bike
the translators both use clasp_make_integer, so it seems like it should fail, unelss there's an overload i guess
19:55:45
shiho
In energyNonbond.cc, does dA mean LJ A-coefficients and dC mean LJ B-coefficients?
19:58:23
drmeister
Bike: clasp_make_integer is almost certainly the problem - it's casting everything to a uint64_t.
19:58:40
drmeister
I think Integer_O::create(...) is what should be used - there are many overloads for that.
20:01:35
drmeister
I don't know what I was thinking there.
20:01:42
drmeister
Bad copy-paste - probably.
20:05:18
drmeister
shiho: I hope so - but I can't find any documentation that supports this.
20:07:47
Bike
yeah, but now i don't know why it's working
20:35:14
drmeister
stassats: I haven't seen that error - could you paste the build log?
20:35:32
drmeister
I'm working on more robust, lower-cost backtraces that might help us here.
20:50:35
stassats
well, i'm no longer building it
0:28:10
drmeister
I have the backtraces working now:
0:28:12
drmeister
https://www.irccloud.com/pastebin/dNSz6kAo/
0:35:25
drmeister
The function names have zero runtime cost. Function names are now associated with frames from JITted code. In cclasp - arguments are saved when a function has (declare (debug 3)).
0:35:41
drmeister
Saving arguments has a runtime cost.
5:31:27
beach
Good morning everyone!
Thursday, 21st of September 2017, 6:00:44 UTC