02:55 ilbot3 joined 03:03 MasterDuke joined 03:08 releasable6 joined 05:38 evalable6 joined 06:17 domidumont joined, domidumont1 joined 06:25 domidumont joined 06:43 geospeck joined 07:12 geospeck joined 08:00 brrt joined 08:04 geospeck joined, domidumont joined 08:26 zakharyas joined 08:33 zakharyas joined
brrt good * #moarvm 08:50
i've counted and if i'm packing even a bit loosely, i could easily encode most of the info that currently lives in the expr node info structure into the expr operand itself 08:52
this would save memory, but more importantly, random memory accesses
if i'm packing tightly then i've got room to spare 08:53
nwc10 good *, brrt 08:57
sounds useful - callgrind would give you numbers, but would take a while to do so :-)
brrt true 09:53
and the object is to have the optimizer or spesh-relevant info in a separate hash table since it's really sparse
also, so that during modification i don't immediately have to the info array whenever i'm changing the nodes array 09:54
10:11 geospeck joined 10:36 geospeck joined
lizmat m: sub a() { await start { return } }; a # hmmm, jnthn ? 11:33
camelia MoarVM panic: Internal error: Unwound entire stack and missed handler
jnthn Already ticketed somewhere, but yeah, I'd not expect that to work out well 11:34
lizmat jnthn: I was wondering about the significance of "anon sub THREAD-ENTRY()" in Thread.pm
1. why is that a sub and not just a block, and 2. why anon?
jnthn 1. because it having a name in the backtrace is really useful and maybe even relied upon in the backtrace heuristics, and 2. 'cus we only want the name on the sub, not to install it somewhere 11:35
lizmat ok, so it was not intended to catch any "return" from the started code ? 11:37
jnthn It couldn't 11:38
return is resolved purely lexically
lizmat TIL 11:39
BTW, is "sub a() { await start { return } }; a" worth an Issue ? 11:40
jnthn It's already filed somewhere 11:41
lizmat ack
jnthn: is it correct that no code gets executed after github.com/rakudo/rakudo/blob/mast...ead.pm#L31 ever ? 11:43
11:45 geospeck joined
jnthn Not sure I follow 11:47
I mean, if you put code after it, it'll run
But only if the code() returns
Which for any thread pool thread, it never will
Because they sit in an infinite loop
Reading from the work queue
lizmat ah, duh 11:49
when I do a start block, it doesn't actually run its own thread, it just adds a task 11:50
duh
jnthn :) 11:56
11:58 brrt joined 12:29 AlexDaniel joined 12:57 domidumont joined 13:41 greppable6 joined, domidumont joined 13:56 zakharyas joined 14:13 brrt joined 14:23 greppable6 joined 14:26 brrt joined
dogbert2 hmm, t/spec/S17-promise/stress.t has a tendency to hang when run with MVM_SPESH_BLOCKING=1 14:32
15:18 brrt joined 16:14 brrt joined
ugexe github.com/libuv/libuv/issues/1625 - any ideas? we'll be stuck to 1.14.2 (which requires a revert) otherwise 16:20
16:27 geospeck joined
brrt looking 16:38
yay, i found a bug in expr_ops 16:39
and the solution isā€¦ let's do the nonzero-field trick everywhere 16:41
17:06 zakharyas joined
jnthn hm, not having much luck with github.com/MoarVM/MoarVM/issues/749 17:07
17:07 domidumont joined
jnthn Thought I knew what might be going on but...no 17:07
I can't figure out where there's a moment it's unmarked
Will dig more tomorrow 17:09
ugexe oh i may have solved the libuv thing
nwc10 jnthn: that's "ok 62 - CLOSE phaser sees correct outer scope" ? 17:11
ASAN refuses to make any comment :-( 17:12
jnthn Yeah 17:16
valgrind reliably triggers
Gotta head home now though...will look at it some more in the morning :) o/ 17:17
nwc10 yes. a fresh head feels like the right pan
plan
17:39 brrt joined 18:17 zakharyas joined 18:23 geospeck joined 18:48 TimToady joined 19:01 geospeck joined
lizmat wonders if it isn't time for a MoarVM version bump? 20:21
(looks like it's 13 commits behind)
Zoffix bumps
jnthn That's an unlucky number. Let's wait for 14. ;) 20:22
lizmat cool
hehe
it's at 70, that's already 5x 14 :-)
20:28 releasable6 joined 20:35 patrickz joined, robertle joined 20:48 AlexDaniel joined
Geth MoarVM: ugexe++ created pull request #752:
Revert "Use uv_fs_copyfile API"
21:18
21:46 zostay_ joined 21:49 BinGOs_ joined 21:53 leedo joined 21:54 unicodable6 joined 21:56 squashable6 joined 22:07 ilmari[m] joined
lizmat and another Perl 6 Weekly hits the Net: p6weekly.wordpress.com/2017/11/13/...explained/ 22:11
22:17 MasterDuke joined 22:21 benchable6 joined, coverable6 joined 22:22 quotable6 joined, bisectable6 joined, releasable6 joined, committable6 joined, nativecallable6 joined 22:29 squashable6 joined 22:30 Ven joined 22:39 AlexDaniel` joined 23:16 statisfiable6 joined 23:27 statisfiable6 joined
MasterDuke is MVMStringBody.num_graphs guaranteed to always be correct? 23:59