github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
00:13 sena_kun left 00:27 Kaeipi left, sena_kun joined 00:28 Kaeipi joined 01:41 vrurg_ is now known as vrurg 02:14 sena_kun left 02:30 sena_kun joined 04:15 sena_kun left 04:30 sena_kun joined 04:56 Kaeipi left 04:57 Kaeipi joined, Kaeipi left 04:58 Kaeipi joined 06:14 sena_kun left 06:30 sena_kun joined 07:31 sourceable6 left, nativecallable6 left, greppable6 left, notable6 left, releasable6 left, quotable6 left, benchable6 left, coverable6 left, tellable6 left, reportable6 left, bisectable6 left, bloatable6 left, statisfiable6 left, squashable6 left, shareable6 left, evalable6 left, committable6 left, unicodable6 left 07:32 statisfiable6 joined, unicodable6 joined, shareable6 joined, benchable6 joined, nativecallable6 joined, quotable6 joined 07:33 sourceable6 joined, notable6 joined, greppable6 joined, committable6 joined, releasable6 joined, coverable6 joined, squashable6 joined, evalable6 joined 07:34 bisectable6 joined, reportable6 joined, tellable6 joined, bloatable6 joined 08:04 domidumont joined 08:14 sena_kun left 08:28 sena_kun joined 09:15 Voldenet left 10:14 sena_kun left 10:28 sena_kun joined 12:14 sena_kun left 12:29 sena_kun joined 12:40 Voldenet joined, Voldenet left, Voldenet joined
Geth_ MoarVM: e224567df8 | (Stefan Seifert)++ | docs/ChangeLog
Update ChangeLog for 2019.12 release
13:21
nine I went through the release guide and finished all steps except for the ones about signing and tags. Looks like everything's fine 13:29
sena_kun nine++ 13:32
13:40 evalable6 left, evalable6 joined
sena_kun we do need to finish the process properly, though. as for github.com/rakudo/rakudo/issues/3311 I am not really sure. one thing it can be reproduces on macos, another one it reproduces on some macos setups, excluding MBP in question. 13:45
14:13 sena_kun left 14:29 sena_kun joined
nine Apparently the test in question has long been troublesome: rt.perl.org/Public/Bug/Display.html?id=130042 14:43
But this commit actually gives a hint about what may be the issue again: github.com/rakudo/rakudo/commit/49fd82517f 14:45
And indeed, I can reproduce it by adding a sleep 1; after the nqp::buildnativecall! 14:46
16:14 sena_kun left 16:29 sena_kun joined
nine Apparently there is still one more side effect of my callback deopt fix: exceptions (even control exceptions like return) don't find a handler. 17:32
dogbert2 m: sub { await start { return } }() 17:48
camelia MoarVM panic: Internal error: Unwound entire stack and missed handler
18:13 sena_kun left 18:28 sena_kun joined
nine It's....gone? Cannot reproduce it anymore 18:32
Could on my desktop. Then wanted to repro on my laptop for rr but there it worked just fine. Then I noticed that I actually had a local change to Inline::Perl5 that could explain perfectly why I didn't see the missed handler message: I removed the return from the exact callback that I saw failing on the desktop 18:34
But, reverting that change didn't bring on the failure and after trying the same change on my desktop, the failure is gone there, too. Even after I reverted it again!
So maybe the recompile fixed it 18:38
Geth_ MoarVM: 2ac1fa27f5 | (Stefan Seifert)++ | src/core/nativecall.c
Fix race condition with multi threaded NativeCall users

A NativeCall site is considered set up as soon as its body->lib_handle is non-NULL. If we initialize lib_handle too early, a different thread might think everyting's already set up and run into strange issues. So instead, initialize it last, after everything else is done.
18:44
nine This is just an extension of the fix for github.com/rakudo/rakudo/issues/3311
lizmat nine++ 18:45
dogbert2 nine++, soon there won't be any bugs left :) 18:46
18:56 domidumont left 19:13 domidumont joined 19:53 zakharyas joined 19:58 domidumont left 20:14 sena_kun left 20:30 sena_kun joined 21:26 zakharyas left 21:55 Kaeipi left 21:56 Kaeipi joined 21:57 domidumont joined 21:59 domidumont left 22:14 sena_kun left 22:28 sena_kun joined 23:28 sena_kun left