00:42
leedo joined
01:38
TimToady joined
01:56
ilbot3 joined
05:06
brrt joined
|
|||
brrt | so, adding a 'discard' node prior to the write barrier works | 05:08 | |
yoleaux | 22 Oct 2017 23:27Z <samcv> brrt: can you add what you would like to the changelog for the expression engine? You'd be the best one to know what should be added to the changelog | ||
brrt | .ask samcv where should i write it? in the repo? | 05:09 | |
yoleaux | brrt: I'll pass your message to samcv. | ||
brrt | oh, you just edit docs/Changelog | 05:12 | |
i will | |||
AlexDaniel` | brrt++ | 05:24 | |
Geth | MoarVM/jit-expr-optimizer: 4 commits pushed by (Bart Wiegmans)++ | 05:26 | |
brrt | only the last two commits are unique, rest is a rebase | 05:27 | |
the tl;dr, we can optimize multiple loads to a copy, and this does seem to lead to less memory traffic | 05:30 | ||
05:45
evalable6 joined
|
|||
Geth | MoarVM: 1525165e41 | (Bart Wiegmans)++ | docs/ChangeLog Rearrange changelog entries for expression JIT |
05:48 | |
06:17
brrt joined
|
|||
brrt | adhoc templates is one of those things that i should've done much sooner | 06:31 | |
nine | brrt: I should have read Practical Lessons in Leadership 10 years ago. Try to beat that ;) | 06:48 | |
brrt | what kind of book is that | ||
… by art petty and rich petro | 06:49 | ||
those names though | |||
also, good morning | 06:50 | ||
nine | It's...exactly what the title says. It's all those things that would have been so useful when I first became a team leader. Anyway, they are still useful now :) | 06:51 | |
And yes, good morning! | |||
AlexDaniel` | .oO( it's not a name if it's ≤10 characters! ) |
||
nine | AlexDaniel`: www.kalzumeus.com/2010/06/17/falseh...out-names/ ;) | 06:53 | |
AlexDaniel` | there was another similarly good one: infiniteundo.com/post/25326999628/f...about-time | 06:57 | |
although some of its falsehoods border with total stupidity | 06:58 | ||
like, I really wonder if there are any programmers who don't know about february… hmm | |||
07:02
domidumont joined
07:08
domidumont joined
|
|||
brrt | i think that's not about not knowing about it, it's about assuming the issue isn't very problematic | 07:29 | |
eh | |||
the difference doesn't matter, i mean | |||
07:31
rba joined
07:46
committable6 joined
07:48
committable6 joined
07:49
zakharyas joined
08:06
rba joined
08:14
domidumont joined
08:18
zakharyas joined
08:41
rba joined
09:11
domidumont joined
09:12
brrt joined
10:25
greppable6 joined
|
|||
samcv | brrt, yeah in the repo. thanks! | 10:32 | |
brrt | :-) | ||
samcv heads back to bed | 10:43 | ||
brrt | sleep well | 10:49 | |
timotimo | hum. | 10:52 | |
Geth | MoarVM: 5d2ee22e66 | (Timo Paulssen)++ | src/instrument/crossthreadwrite.c don't memcmp where it should strncmp in crossthreadwritelog |
11:59 | |
lizmat | MoarVM panic: Heap corruption detected: pointer 0x10ea11e50 to past fromspace # whee! | 12:06 | |
MoarVM panic: Internal error: zeroed target thread ID in work pass | 12:16 | ||
MoarVM panic: Heap corruption detected: pointer 0x1032e80a8 to past fromspace | 12:18 | ||
just posting results of runs | |||
brrt | hmmm. results of what? | 12:19 | |
*runs of what | |||
lizmat | github.com/rakudo/rakudo/issues/1202 | ||
Segmentation fault: 11 | 12:25 | ||
12:32
brrt joined
|
|||
timotimo | is that with the crossthreadwrite log enabled? it might be explosive still | 12:37 | |
(and if you don't MVM_SPESH_BLOCKING it, it's even more explosive) | |||
lizmat | no, this is just running on HEAD | ||
timotimo | urgh | 12:38 | |
12:42
zakharyas joined
12:43
zakharyas joined
12:57
unicodable6 joined
13:10
brrt joined
13:32
brrt joined
14:00
Zoffix joined
14:01
Zoffix left,
Zoffix joined
14:06
brrt joined
14:15
ggoebel joined
14:19
patrickz joined
14:33
rba_ joined
|
|||
lizmat | the code of github.com/rakudo/rakudo/issues/1202 now usually crashes in MoarVM space (and a lot less than before) | 14:47 | |
it now typicall always is: MoarVM panic: Heap corruption detected: pointer 0x1105d27d0 to past fromspace | 14:48 | ||
15:07
brrt joined
|
|||
AlexDaniel` | fwiw I tested it here also and sometimes it also hangs | 15:18 | |
in fact, most of the time it hangs | 15:19 | ||
lizmat | I've just had a hang in S07-hyperrace/race.t, test 29 | 15:20 | |
AlexDaniel` | hmm | ||
lizmat | I ran a sample of the process: gist.github.com/lizmat/d22cfb0c67f...3b7187c15e | ||
hope this is of help to somehow with moar gut internals knowledge | |||
16:00
brrt1 joined
|
|||
AlexDaniel` | fwiw changelog things: “seakable” → “seekable” and some lines have tabs | 16:02 | |
timotimo | we should be able to tease out the exact location where things go wrong by lowering nursery size and crossing fingers | 16:03 | |
16:04
domidumont joined
16:20
brrt joined
16:21
dogbert17 joined
|
|||
lizmat | timotimo: see my thoughts on that on #perl6-dev just now | 16:35 | |
timotimo | does .elems sometimes cause autovivification? | ||
moritz | it shouldn't | 16:36 | |
only writing accesses should autovivify | |||
timotimo | i mean for internally-used attributes, not for the list's storage | ||
Zoffix | It can cause reification | 16:38 | |
lizmat | the thing is that .elems may cause changes in attributes of a List | ||
Zoffix | m: my @l := List.from-iterator: (gather { say "meow"; take 1; }).iterator; say "starting"; @l.elems.say; say "done" | ||
camelia | starting meow 1 done |
||
timotimo | Zoffix: at least in the context of the ThreadPoolScheduler i don't think the lists actually have iterators involved in 'em? | ||
lizmat | because .elems may reify | ||
Zoffix | Ah. No idea :) | 16:39 | |
lizmat | it's not about iterators | ||
it's about .elems calling reify-until-lazy | |||
and if fully reified, resetting $!todo | |||
16:44
ggoebel joined
16:50
rba joined,
zakharyas joined
17:08
zakharyas joined
|
|||
Geth | MoarVM: 6e59a07653 | (Samantha McVey)++ | docs/ChangeLog Add further entries to ChangeLog |
18:53 | |
lizmat | .tell jnthn I wonder whether the difference between .hyper and .race is really whether results are buffered or not | 19:55 | |
yoleaux | lizmat: I'll pass your message to jnthn. | ||
lizmat | .tell jnthn I could see .race internally working as a Supply, emitting values from several threads as they become available | ||
yoleaux | lizmat: I'll pass your message to jnthn. | ||
lizmat | .tell jnthn instead of .pushing to an IterationBuffer until the end of the batch | 19:57 | |
yoleaux | lizmat: I'll pass your message to jnthn. | ||
timotimo | lizmat: performance is much better if you submit big batches of data compared to individual pushes (for example to a supply) | 20:08 | |
lizmat | timotimo: yeah, but if you have a serializer at the end of the chain that does post-processing, you would like the values to appear gradually, rather than in blocks | 20:09 | |
perhaps, not always I guess | |||
timotimo | samcv: i think the "left-over calloc in NFA" is a fix to a feature that's also new in this version; an oversight that was more or less quickly fixed? | 20:11 | |
samcv | ah ok i can remove it then | ||
timotimo | in fact, it's the commit right before it: 054ad4e and the original work in 3059ba2829 | ||
samcv | thanks | 20:12 | |
timotimo | using FSA in the NFA might be noteworthy, but probably not | ||
starting to use FSA in the VMArray impl will have a much bigger impact, for example | |||
thanks for doing the release work :) | |||
cognominal | m: say $/.^name | 21:11 | |
camelia | Nil | ||
cognominal | m:'a' ~~ /a/ say $/.^name; say $/.^role | 21:12 | |
evalable6 | (exit code 1) ===SORRY!=== Error while compiling /tmp/cNH0Xg9Mx1 Two ter… |
21:13 | |
cognominal, Full output: gist.github.com/d7c4524130f2d246ea...eff546f314 | |||
cognominal | m:'a' ~~ /a/; say $/.^name; say $/.^role | ||
evalable6 | (exit code 1) Match No such method 'role' for invocant of type 'Perl6::Metamodel::ClassHOW'. Did you mean any of these? none note one roles in block <unit> at /tmp/UlHPkcm3Zc line 1 |
||
cognominal | m:'a' ~~ /a/; say $/.^name; | ||
evalable6 | Match | ||
cognominal | m:'a' ~~ /a/; say $/.^roles; | ||
evalable6 | (exit code 1) Unexpected named argument 'transitive' passed in block <unit> at /tmp/ZXYhBGq0yJ line 1 |
||
cognominal | m:'a' ~~ /a/; say $/.^roles; | 21:14 | |
evalable6 | (exit code 1) Unexpected named argument 'transitive' passed in block <unit> at /tmp/vJi3P3aNh7 line 1 |
||
cognominal | m: say $/.^roles; | 21:16 | |
camelia | () | ||
cognominal | m:'a' ~~ /a/; say $/.^roles; | ||
evalable6 | (exit code 1) Unexpected named argument 'transitive' passed in block <unit> at /tmp/3z9nwNPSjz line 1 |
||
lizmat | and another Perl 6 Weekly hits the Net: p6weekly.wordpress.com/2017/10/23/...ds-racing/ | 21:38 | |
21:54
evalable6 joined
22:59
Voldenet joined
|