[00:03] *** reportable6 left [00:04] *** reportable6 joined [00:35] *** jgaz joined [01:21] *** jgaz left [02:18] *** Kaiepi left [02:18] *** Kaipi joined [04:11] *** japhb left [04:14] *** japhb joined [05:14] *** sourceable6 left [05:14] *** bloatable6 left [05:14] *** greppable6 left [05:14] *** statisfiable6 left [05:14] *** unicodable6 left [05:14] *** reportable6 left [05:14] *** evalable6 left [05:14] *** tellable6 left [05:14] *** committable6 left [05:14] *** squashable6 left [05:14] *** linkable6 left [05:14] *** reportable6 joined [05:15] *** evalable6 joined [05:15] *** squashable6 joined [05:15] *** tellable6 joined [05:15] *** statisfiable6 joined [05:15] *** greppable6 joined [05:16] *** sourceable6 joined [05:16] *** linkable6 joined [05:16] *** unicodable6 joined [05:16] *** bloatable6 joined [05:16] *** committable6 joined [06:02] *** reportable6 left [06:04] *** reportable6 joined [07:02] *** gfldex joined [07:43] good *, #moarvm [08:10] *** patrickb joined [08:12] *** dogbert17 joined [08:12] *** dogbert11 left [08:35] *** squashable6 left [08:37] *** squashable6 joined [09:27] moarning o/ [09:27] \o [09:45] Uff, what a hack, but I can get NQP to rebootstrap on new-disp [09:57] Seems we're going to need two rebootstraps also to fully eliminate things [10:00] The joys of bootstrapping when not all parts of the program are actually bootstrapped... [10:00] I'm making sure I didn't break the JVM build before I rebootstrap on MoarVM [10:01] It might not be hard to untangle later but it might well be [10:14] Seems all's well, so rebootstrapped and now some stuff can start being removed :) [10:15] Although I should stop working on this and prepare for this afternoon's job... :) [10:24] We've lost one spectest, but turns out it's because of a missing change from master. [11:08] *** sena_kun joined [12:02] *** reportable6 left [12:05] *** reportable6 joined [12:26] *** dogbert11 joined [12:28] *** dogbert17 left [12:53] *** MasterDuke joined [13:54] spectest run with asan and 4k nursery completed [14:00] That must take a while [14:02] it did indeed. I see one heap buffer overflow. [14:03] And that was it, or some panics/segvs too? [14:03] interested parties can take a peek here: https://gist.github.com/dogbert17/3cc911045a857bf78093822612b50a24 [14:04] a few panics as well, not too many though [14:04] ooh, interesting [14:04] Dunno if it's enough information but hopefully it is [14:05] It's a very good lead, at least [14:05] Let me know if more info is needed [14:05] realloc of wrong size? [14:06] I guess that you both have timos' linikify script installed [14:07] i do [14:08] it's very useful [14:08] I've found a nasty GC issue in push_resumption. It calls resume_init_capture which will allocate an MVMCapture, but resume_data holding the arguments is not anchored anywhere, so those args won't get marked [14:09] hello nine [14:09] nine: Hm, they're not part of something (e.g. a register set) that is marked? [14:10] MasterDuke: but then again I think it assumes master so it won't show new-disp code :( [14:10] Need to work on something else for a little bit, but will glance later [14:10] Not yet. We're in the process of setting up. [14:10] yeah, wondered why the line number wasn't right at first [14:12] we have an MVM_recalloc, but there are a bunch of cases of MVM_realloc+immediate memset 0 [14:12] nine: stumbled upon a GC error which seems to point towards MVM_args_slurpy_positional [14:13] the stacktrace look like this: [14:13] #0 MVM_panic (exitCode=exitCode@entry=1, messageFormat=messageFormat@entry=0x7ffff68401e0 "Collectable %p in fromspace accessed") at src/core/exceptions.c:854 [14:13] #1 0x00007ffff64d6c23 in MVM_VMArray_push (tc=, st=, root=, data=0x621000005fb8, value=..., kind=) at src/6model/reprs/VMArray.c:496 [14:13] #2 0x00007ffff633ab42 in MVM_args_slurpy_positional (tc=0x618000000080, ctx=, pos=) at src/core/args.c:1092 [14:15] dogbert11: that may not mean anything. As long as outdated values make it into registers, they will show up in all sorts of places [14:18] so the trace could be a red herring then [14:28] ha! `git checkout -b convert_realloc_plus_memset_0_to_recalloc` [14:28] `fatal: A branch named 'convert_realloc_plus_memset_0_to_recalloc' already exists.` [14:29] from 2017. apparently i have very consistent naming [15:10] <[Coke]> HA [15:33] OK, I'm back to new-disp [15:36] "guess who's back, back again, jnthnwrthngtn's back, tell a friend" [16:17] ¦ MoarVM/new-disp: 9d7314a2fd | (Jonathan Worthington)++ | 22 files [16:17] ¦ MoarVM/new-disp: Remove the multiple dispatch cache [16:17] ¦ MoarVM/new-disp: [16:17] ¦ MoarVM/new-disp: The new-disp branches of NQP and Rakudo no longer rely upon it. Also [16:17] ¦ MoarVM/new-disp: go a little further in spesh and remove invocation protocol handling [16:17] ¦ MoarVM/new-disp: also. [16:17] ¦ MoarVM/new-disp: review: https://github.com/MoarVM/MoarVM/commit/9d7314a2fd [16:30] huh, how on earth did istrue/isfalse ended up getting compiled into the new bootstrap [16:36] *** patrickb left [16:37] * jnthnwrthngtn is confused [16:37] Maybe it needed another trip around the bootstrap loop to get rid of entirely [16:38] ¦ MoarVM/remove-istrue: 353fb90e70 | (Jonathan Worthington)++ | 11 files [16:38] ¦ MoarVM/remove-istrue: Remove if_o, unless_o, istrue, and isfalse [16:38] ¦ MoarVM/remove-istrue: [16:38] ¦ MoarVM/remove-istrue: And the boolification routine that underlies them. They are all replaced [16:38] ¦ MoarVM/remove-istrue: by a new-disp based mechanism. [16:38] ¦ MoarVM/remove-istrue: review: https://github.com/MoarVM/MoarVM/commit/353fb90e70 [16:38] Guess it can wait :) [16:42] * MasterDuke admits /me sometimes runs `make m-bootstrap-files; ; make m-bootstrap-files` a couple times before committing the new files [16:43] is(true|false)_s aren't being removed? [16:45] and sp_istrue_n? [16:46] well, the istrue|false_s and n are not polymorphic [16:46] The good news is that the push_resumption bug seems to be the actual source of the GC issues. Bad news is that so far I haven't come up with a pretty way to solve it. [16:46] Just a working one [16:46] those work on registers that cannot have types of things [16:49] MasterDuke: Correct, those are staying, for the reason timo said [16:50] ah. so it does make sense to jit them then? [16:51] is(true|false)_s [16:52] I think we do JIT istrue_s and isfalse_s [16:52] dispatchers are a superpower when you want to find some code to run where the choice depends on the details of the type something has and that can be "always the same" or "usually the same" in consecutive executions [17:08] Tracking down the last things that rely on the invocation protocol stuff in MoarVM. Turns out...p6capturelex does, in order to find the code attribute in order to capturelex it [17:10] we have templates for is(true|false)_s, but they're not implemented in the lego jit [17:10] ah, ok. I thought I'd just seen them in jit stuff somewhere :) [17:13] urgh, p6capturelex is kinda horrible [17:13] Though I wonder if any of the things it's defending against ever actually go wrong. If they do something is weird [17:14] p6capturelexwhere is worse [17:15] I guess both could become a dispatchers and the VM glue can become a syscall and then both extops can go away [17:16] how many extops left then? [17:16] Oh my, and then there's two further ops dabbling in weird scoping stuff too [17:17] There's currently 12 in total [17:17] So we're not that far of getting rid of 'em [17:17] *off [17:17] nice [17:19] Goodness, this lot will be quite the pain [17:22] Guess it'll be tomorrow's task [17:23] I'm tired [17:23] But pushed the invocation protocol removal so I'll have that work to hand tomorrow (will probably work from the office tomorrow, thus why I'm not just keeping these various "still need other work first" bits locally) [17:25] I'm kinda figuring that if I can eliminate the invocation protocol stuff in MoarVM also, and also the classic invoke ops (and getting rid of the one caes of invokewithcapture that remains) then I might have an easier time of adapting spesh [17:37] m: dd "a b" cmp ("a","b") # do we consider that to be correct ? [17:37] rakudo-moar 50bd1717c: OUTPUT: «Order::Same␤» [17:38] jnthnwrthngtn: you feel the need for a change of coffee? [17:41] lizmat: that doesn't seem right [17:41] yeah, feels meh to me as well [17:52] *** sena_kun left [18:02] *** reportable6 left [18:05] *** reportable6 joined [18:09] Nicholas: I'm not sure dal counts as a coffee... :) [19:49] *** japhb left [19:56] *** japhb joined [21:06] ¦ MoarVM/new-disp: a15aa367d2 | (Jonathan Worthington)++ | 14 files [21:06] ¦ MoarVM/new-disp: Remove smrt_[int|num|str]ify ops [21:06] ¦ MoarVM/new-disp: [21:06] ¦ MoarVM/new-disp: A mostly straightforward removal. However, the configuration program [21:06] ¦ MoarVM/new-disp: generator will need a tweak for this; I think it will be a simple one. [21:06] ¦ MoarVM/new-disp: review: https://github.com/MoarVM/MoarVM/commit/a15aa367d2 [21:06] timo: ^^ tweaked the conf program ops, in a way that I think will be OK (at least easy to adapt) [21:10] If anybody wants an LHF-ish, I suspect that we can get away with deprecating the tryfindmeth op at this point [21:11] (In MoarVM. In NQP the op exists but compiles into a dispatcher.) [21:12] There's actually two ops, tryfindmeth and tryfindmeth_s [21:12] Also likely can and can_s can go away too [21:14] kick the can_s down the road, or off the bridge, or something [21:20] m: say 4119400 - 4080584 [21:20] rakudo-moar 50bd1717c: OUTPUT: «38816␤» [21:21] 38KB smaller NQP build output from not building the legacy method caches on MoarVM, it seems. I expected maybe a bit more. Though probably will be more dramatic in Rakudo [21:21] ooh, intersting, and some test fails [21:21] Well, time to be afk [22:33] *** evalable6 left [22:33] *** linkable6 left [22:33] *** evalable6 joined [22:34] *** linkable6 joined [23:54] *** evalable6 left [23:54] *** linkable6 left [23:55] *** linkable6 joined [23:57] *** evalable6 joined