Welcome to the main channel on the development of MoarVM, a virtual machine for NQP and Rakudo (moarvm.org). This channel is being logged for historical purposes.
Set by lizmat on 24 May 2021.
00:07 reportable6 left 00:09 reportable6 joined
moon-child re warning: apparently it's a gcc bug 00:21
00:31 Kaiepi left, Kaiepi joined 00:57 Altai-man joined 00:59 sena_kun left 01:59 bisectable6 left, sourceable6 left, committable6 left, benchable6 left, releasable6 left, bloatable6 left, unicodable6 left, coverable6 left, shareable6 left, greppable6 left, nativecallable6 left, linkable6 left, tellable6 left, statisfiable6 left, evalable6 left, reportable6 left, quotable6 left, notable6 left 02:00 nativecallable6 joined, quotable6 joined, statisfiable6 joined, greppable6 joined, shareable6 joined, benchable6 joined 02:01 sourceable6 joined, bloatable6 joined, notable6 joined, tellable6 joined, committable6 joined, releasable6 joined, unicodable6 joined, evalable6 joined, coverable6 joined 02:02 reportable6 joined, bisectable6 joined, Altai-man left, linkable6 joined 02:07 sena_kun joined 02:08 Altai-man joined 02:12 sena_kun left 03:35 Kaiepi left 04:01 Kaiepi joined 04:28 Kaiepi left 04:58 frost joined 05:07 frost left 05:22 kjp left 05:37 kjp joined 05:46 kjp left 05:47 kjp joined
Nicholas [* GOOD *] 05:49
06:07 reportable6 left 06:08 reportable6 joined 08:44 Kaiepi joined 09:59 sena_kun joined 10:59 evalable6 left, linkable6 left 11:01 linkable6 joined 11:02 evalable6 joined 11:25 frost joined 12:07 reportable6 left 12:08 reportable6 joined
vrurg m: class C { method foo(--> Nil) { }; method p(&code) { LEAVE self.foo; code() }; method bar { self.p({ return 42 }) }; }; say C.new.bar; 13:15
camelia foo
vrurg Is it by design???? jnthnwrthngtn? 13:16
jnthnwrthngtn vrurg: Probably a case of github.com/rakudo/rakudo/issues/4521 14:17
vrurg It's in the way of my work on fixing CU/require concurrency. 14:19
Though I can rework the problematic code to get the returns out of the protected blocks, but it would likely slightly de-optimize them. Is there a workaround for the bug? 14:21
jnthnwrthngtn Not besides what you suggested, alas 14:23
vrurg Do you at least know if it's in the current codegen code and would be different on RakuAST? I mean, does it make sense for me to try fixing it? 14:25
14:26 frost left
jnthnwrthngtn I was more planning to re-work how LEAVE time is done generally, but it's an all-the-stack kind of change. I don't think it's a code-gen bug, probably more a MoarVM one, but not sure. 14:26
vrurg Ok, then I better change the CU code. There are only two or three locations left. 14:28
BTW, if there is a better suggestion for Lock::Soft name I'd like to consider it. :) 14:29
One more on this. Lock.protect is not affected. I presume because nqp::unlock doesn't touch the stack. 14:37
15:19 Kaiepi left 15:20 Kaiepi joined
jnthnwrthngtn What is Lock::Soft? 15:20
vrurg await-based replacement for Lock. 15:49
vrurg is afk for a couple of hours
17:17 sena_kun left 18:06 reportable6 left 18:08 reportable6 joined 19:43 vrurg left
nine nine@sphinx:~/rakudo (rakuast_wip *)> RAKUDO_RAKUAST=1 ./rakudo-m -Ilib -e 'use Test;' 19:54
nine@sphinx:~/rakudo (rakuast_wip *)>
It compiles!
Nicholas ship it! 19:58
19:59 vrurg joined
japhb Awesome! nine++ 20:02
MasterDuke nice 20:16
moon-child: interesting, where are you seeing that? 20:24
moon-child MasterDuke: I don't remember; but there was some gcc bug that was causing it to think array bounds were being overrun, that was affecting a lot of projects
MasterDuke src/disp/inline_cache.c:646:19: warning: array subscript ‘MVMDispInlineCacheEntryPolymorphicDispatchFlattening[0]’ is partly outside array bounds of ‘MVMDispInlineCacheEntry[1]’ [-Warray-bounds] 20:26
  646 |         MVMuint32 num_dps = ((MVMDispInlineCacheEntryPolymorphicDispatchFlattening *)entry)->num_dps;
      |                   ^~~~~~~
i've gotten ^^^ for a while now, but some googling did suggest it was a gcc bug. i'd hoped it would disappear with 12, but it hasn't. the other one is new with gcc 12 20:27
20:36 Altai-man left
MasterDuke lwn.net/Articles/893686/ "Modern Python performance considerations", but might be some stuff of interest for us 20:36
20:41 sena_kun joined 21:26 uzl[m] joined 22:17 Altai-man joined, sena_kun left 23:17 Kaiepi left 23:19 Kaiepi joined 23:45 Kaipei joined 23:48 Kaiepi left