01:49 ilbot3 joined 01:51 geekosaur joined 01:54 colomon_ joined
samcv pasted this in perl6-dev but 02:18
looks like moarvm doesn't have a point release. and we have 2017.04.3 but no newer tagged version of moarvm 02:19
or nqp. since the fixed in .3 needed updates to moarvm
do we want to make a point release so distros can update moarvm/nqp and thus get 2017.04.3? seems it would make sense 02:24
MasterDuke_ 2017.05 is only about a week away... 02:31
samcv ok 02:57
so we just wait until 2017.05? i mean still it's weird for a tagged release to not be able to be installed based on other tags 02:58
i mean it's easy enough to add tags for the nqp and moarvm revisions on which it depends on 03:01
04:39 colomon joined 05:31 brrt joined 05:45 domidumont joined 05:50 domidumont joined 05:54 domidumont joined
brrt ugh, i found a new bug 06:03
samcv such is life 06:10
06:28 geekosaur joined 06:42 brrt joined 07:04 lizmat joined
brrt it's always a bit dissapointing, though, when the bug turns out to be so… banal 07:15
hehe, bug! 07:29
i do wonder why the jit bisection script just won't work on OS X 07:49
samcv what's it written in? 07:56
Geth MoarVM/even-moar-jit: b1c982f726 | (Bart Wiegmans)++ | 4 files
Fig call arg resolution bug

CALL and CALLV nodes can use register arguments and those can conflict with ARGLIST parameters. So, they have to be moved out of the way. However, I mistakenly used the (constant value) args rather than the register numbers, so this didn't quite work.
08:01
MoarVM/even-moar-jit: 2d82ae7058 | (Bart Wiegmans)++ | 4 files
Add decont template (uses repr function invocation)

This was kind of tricky because it involves a destructive template and a pointer function call.
brrt perl 08:07
usual old perl
but it seems like stuff just goes wrong somehow
08:08 zakharyas joined
lizmat morning! 08:23
brrt morning lizmat
how's the #pts
lizmat so I want to add the information contained in nqp/gen/moar/stage1/nqp-config.nqp as part of the perl6 -V output 08:24
brrt uhuh
lizmat busy :-)
wish I felt better :-(
brrt wishes you better
lizmat brrt: thanks :-)_ 08:25
probably should ask this on perl6-dev
08:34 Ven joined 08:37 AlexDaniel joined 09:25 robertle joined
brrt this has to be the biggest miscompile i've had so far 09:49
the broken frame nr is 1380\ 09:51
09:55 robertle joined 10:07 Ven joined
samcv i'm gonna add info of the tags to the 2017.04.3 release page. since adding tags for a nonrelease seems no bueno. that will at least tie up that end enough for my satisfaction 10:20
10:45 Ven_ joined 12:34 Ven joined 12:53 Ven_ joined 13:05 brrt joined 13:08 Ven_ joined 13:26 Ven_ joined
brrt my problem looks suspiciously like a missing deopt check, or missing invokish, or something like that 13:53
13:54 Ven joined 14:09 Ven_ joined 14:19 Ven__ joined 15:11 lizmat_ joined 16:05 Ven joined 16:42 domidumont joined 16:44 MasterDuke_ joined 17:11 Ven joined 17:23 Ven_ joined 17:30 avar joined 17:39 Ven_ joined 17:53 Ven_ joined 17:56 zakharyas joined 18:11 Ven joined 18:21 Ven_ joined 18:24 AlexDaniel joined 18:28 Ven_ joined 18:36 Ven_ joined 19:09 Ven joined 19:14 praisethemoon joined 19:35 Ven_ joined 19:53 Ven_ joined
Zoffix m: use Test; like 'foo', none /bar/ 20:27
camelia not ok 1 - text matches '/bar/'

# Failed test 'text matches '/bar/''
# at SETTING::src/core/Junction.pm line 249
# expected: '/bar/'
# got: 'foo'
20:39 Ven joined 21:19 Ven joined
samcv Zoffix, added info about the dev/escape.p6 and dev/unescape.p6 utilities to CONTRIBUTING.md for atom-language-perl6 21:35
if you use those you will never have escaping problems again :)
much easier to edit things when they are in *normal* form and you only have to deal with the regex escapes
21:59 lizmat joined
timotimo i wonder if we can do better when failing to allocate more memory because we're infinitely recursing 22:23
like, figure out if we're mallocing because we're trying to have space for stack frames 22:24
it's problematic because we also allocate other stuff while infini-recursing, so it won't always be the callstack region being expanded that causes the problem 22:32
jnthn And if the frame always escapes the stack by being heap-promoted that approach won't work anyway 22:33
Not to mention that another therad may hit the out of memory condition than the one that infinitely recurses 22:35
*thread
timotimo right 22:38
we could change the out of memory panic function to inspect the TC and instance and such
to see what's currently most expensive
jnthn Maybe but it doesn't get passed tc or instance 22:42
timotimo right. we can add a function that does analysis before, and pass tc whenever we allocate in a way where it's convenient for us to pass stuff 22:43