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:05 [Coke] left 00:06 reportable6 left 00:08 [Coke] joined 00:09 reportable6 joined 01:07 frost joined 02:02 nine left, nine joined 02:57 Techcable left 02:58 Techcable joined 02:59 Techcable_ joined 03:50 Techcable left, Techcable_ left 05:17 Techcable joined 06:07 reportable6 left 06:10 reportable6 joined
Nicholas good *, #moarvm 06:48
08:00 linkable6 left, evalable6 left 08:01 evalable6 joined 08:02 linkable6 joined 09:29 frost left 10:47 reportable6 left, unicodable6 left, quotable6 left, greppable6 left, releasable6 left, tellable6 left, statisfiable6 left, linkable6 left, evalable6 left, benchable6 left, notable6 left, bloatable6 left, coverable6 left, nativecallable6 left, shareable6 left, committable6 left, bisectable6 left, sourceable6 left 10:48 reportable6 joined, shareable6 joined, nativecallable6 joined, notable6 joined, statisfiable6 joined, sourceable6 joined, committable6 joined 10:49 unicodable6 joined, benchable6 joined, evalable6 joined, bloatable6 joined, tellable6 joined, bisectable6 joined 10:50 coverable6 joined, linkable6 joined, releasable6 joined, greppable6 joined, quotable6 joined 12:07 reportable6 left, reportable6 joined 12:18 frost joined
lizmat and there's another day almost past :-) 12:55
target has a :noinline instruction - ins: param_rp_o
is that an easily fixable inline issue ?
jnthnwrthngtn It's more an argument optimization issue; the argument handling optimization usually rewrites all of those 13:12
So by the time we reach inlining, they ideally are gone (since there's not a good way to inline them)
So the question is "why weren't they written to unchecked parameter instructions" 13:13
Time for me to POETS :) o/ 13:28
lizmat full disclosure: 13:51
2x write_uint32_at BB(7, 68 bytes) -> add_uint32 BB(330):
target has a :noinline instruction - ins: param_rp_o
3x write_uint16_at BB(9, 68 bytes) -> add_uint16 BB(331):
target has a :noinline instruction - ins: param_rp_o
14:12 linkable6 left, evalable6 left, linkable6 joined 14:15 evalable6 joined 15:01 frost left 15:20 frost joined 15:44 frost left
japhb POETS? 17:53
18:08 reportable6 left, [Coke] left, reportable6 joined 18:20 [Coke] joined
MasterDuke lizmat: what's the raku code where you see that? 18:37
lizmat it's from running test-t with -MSIL 18:50
raku -MSIL test-t.pl <hello.csv
Nicholas japhb: en.wikipedia.org/wiki/POETS_day 18:51
"It is tradition to begin the POETS day at 3:30 p.m" is definately [Citation needed] 18:52
MasterDuke huh, i don't see that 18:53
ok, i do on master (i was on my branch that converts a lot of `find_symbol([...], :setting-only)` to `find_symbol_in_setting([...])`) 19:02
japhb Nicholas: Ah, got it! 19:04
MasterDuke hm. none of the obvious things that would cause param_rp_o to not get optimized in src/spesh/args.c seem to be the cause 19:33
20:07 evalable6 left, linkable6 left, linkable6 joined 20:10 evalable6 joined
MasterDuke i seem to get different results with -MSIL and just running with MVM_SPESH_LOG=1. there's no mention of param_rp_o or write_uint* when i do MVM_SPESH_LOG=1 20:33
22:23 linkable6 left, evalable6 left, evalable6 joined 22:25 linkable6 joined 23:45 unicodable6 left, quotable6 left, coverable6 left, benchable6 left, releasable6 left, committable6 left, greppable6 left, bloatable6 left, bisectable6 left, sourceable6 left, reportable6 left, evalable6 left, tellable6 left, statisfiable6 left, nativecallable6 left, notable6 left, linkable6 left, shareable6 left, tellable6 joined, nativecallable6 joined 23:46 releasable6 joined, reportable6 joined, coverable6 joined, shareable6 joined 23:47 evalable6 joined, bisectable6 joined, greppable6 joined, benchable6 joined, statisfiable6 joined, unicodable6 joined 23:48 linkable6 joined, committable6 joined, quotable6 joined, bloatable6 joined, sourceable6 joined, notable6 joined