[00:13] *** stmuk joined
[00:13] *** p6bannerbot sets mode: +v stmuk

[00:15] *** stmuk_ left
[00:32] *** fake_space_whale joined
[00:33] *** p6bannerbot sets mode: +v fake_space_whale

[01:43] *** lizmat left
[02:01] *** stmuk_ joined
[02:02] *** p6bannerbot sets mode: +v stmuk_

[02:04] *** stmuk left
[02:33] *** stmuk joined
[02:34] *** p6bannerbot sets mode: +v stmuk

[02:35] *** stmuk_ left
[03:15] *** fake_space_whale left
[03:29] *** Redfoxmoon left
[03:35] *** Redfoxmoon joined
[03:35] *** p6bannerbot sets mode: +v Redfoxmoon

[04:50] *** Redfoxmoon left
[04:50] *** Redfoxmoon joined
[04:50] *** niven.freenode.net sets mode: +v Redfoxmoon

[04:50] *** p6bannerbot sets mode: +v Redfoxmoon

[05:37] *** brrt joined
[05:38] *** p6bannerbot sets mode: +v brrt

[05:50] *** ZzZombo joined
[05:50] *** p6bannerbot sets mode: +v ZzZombo

[05:51] *** stmuk_ joined
[05:52] *** p6bannerbot sets mode: +v stmuk_

[05:54] *** stmuk left
[06:10] *** robertle joined
[06:10] *** p6bannerbot sets mode: +v robertle

[06:13] *** ZzZombo left
[06:17] *** stmuk joined
[06:18] *** p6bannerbot sets mode: +v stmuk

[06:20] *** stmuk_ left
[06:30] <brrt> \o

[06:31] <nwc10> o/

[06:34] * brrt wants to refactor the expresion compiler but is unsure just how far to go

[06:44] *** ZzZombo joined
[06:44] *** p6bannerbot sets mode: +v ZzZombo

[07:04] *** brrt left
[07:07] <nine> .tell brrt what's the goal of the refactor?

[07:07] <yoleaux> nine: I'll pass your message to brrt.

[08:45] <jnthn> o/

[08:46] <timotimo> o/

[08:56] <nwc10> that's getting unbalanced...

[09:39] *** zakharyas joined
[09:39] *** p6bannerbot sets mode: +v zakharyas

[09:50] *** ZzZombo left
[09:52] *** AlexDaniel joined
[09:52] *** p6bannerbot sets mode: +v AlexDaniel

[09:56] *** brrt joined
[09:56] *** brrt left
[09:58] <AlexDaniel> samcv: ETA? I kinda want to get it off my shoulders

[10:01] *** zakharyas left
[10:19] <dogbert2> \o (trying to balance things up)

[10:29] *** lizmat joined
[10:30] *** p6bannerbot sets mode: +v lizmat

[10:32] *** zakharyas joined
[10:33] *** p6bannerbot sets mode: +v zakharyas

[10:47] *** robertle left
[11:18] *** stmuk_ joined
[11:19] *** p6bannerbot sets mode: +v stmuk_

[11:20] *** stmuk left
[11:21] *** stmuk joined
[11:22] *** p6bannerbot sets mode: +v stmuk

[11:24] *** stmuk_ left
[11:28] *** stmuk_ joined
[11:29] *** p6bannerbot sets mode: +v stmuk_

[11:30] *** stmuk left
[11:38] *** robertle joined
[11:39] *** p6bannerbot sets mode: +v robertle

[12:28] *** stmuk joined
[12:28] *** p6bannerbot sets mode: +v stmuk

[12:30] *** stmuk_ left
[12:35] *** lizmat left
[12:52] *** Kaiepi left
[12:55] *** Kaiepi joined
[12:56] *** p6bannerbot sets mode: +v Kaiepi

[14:14] *** zakharyas left
[15:04] *** brrt joined
[15:05] *** p6bannerbot sets mode: +v brrt

[15:07] <brrt> nine: the main thing is that I want to introduce a new sigil for write-operands

[15:07] <yoleaux> 07:07Z <nine> brrt: what's the goal of the refactor?

[15:07] <timotimo> is this to do with exclamation mark templates or something else?

[15:07] <brrt> yeah, something like that

[15:07] <timotimo> since what expr nodes write isn't really named, right?

[15:08] <brrt> I want it to be obvious that the $0 in a write-operand template is not a value but a reference

[15:08] <brrt> correct

[15:08] <timotimo> oh, like that you mean

[15:08] <brrt> that is the overarching goal

[15:08] <timotimo> so we'd have like >0

[15:08] <brrt> yeah

[15:08] <brrt> I was actually thinking of \$0

[15:08] <timotimo> we don't have ops that have more than one write register operand, right?

[15:08] <brrt> but whatevs :-)

[15:09] <brrt> not yet (maybe never)

[15:09] *** robertle left
[15:10] <brrt> so. I can hack that in, and it'll work....

[15:10] <brrt> but I'm annoyed by the current level of complexity

[15:11] <timotimo> you can just make a \ in front a no-op, and also warn if it's not $0 that follows it :P

[15:11] <brrt> that won't work, the \$0 is parsed as a single token

[15:11] <brrt> and more importantly, I want to capture instance of that missing

[15:12] <timotimo> ah

[15:12] <timotimo> that means the guard ops would become exclamation mark templates, too

[15:12] <timotimo> since they don't necessarily write

[15:12] <brrt> no, no

[15:13] <brrt> a template that doesn't yield any value doens't need an exclamation mark

[15:13] <brrt> it is only templates that *overwrite* the register that is used as their output that need exclamation marks

[15:13] <timotimo> well, guard ops now sometimes write to a different register than they read from

[15:13] <brrt> ah, really?

[15:14] <brrt> guard ops write?

[15:14] <brrt> hmmm

[15:14] <timotimo> yep, if the register differs

[15:14] <timotimo> part of the set elimination optimization i think?

[15:14] <brrt> example?

[15:14] <brrt> oh

[15:14] <timotimo>       [Annotation: INS Deopt One (idx 9 -> pc 464; line 2706)]

[15:14] <timotimo>       sp_guard         r18(1),   r6(9), sslot(1), litui32(464)

[15:15] <jnthn> Guard ops at the point they are inserted will always be two verions of hte same register, but yes, a future set elimination opt might rewrite the instruction

[15:15] <jnthn> And the reason guards do this now is so we have before/after, which lets us do guard elimination

[15:16] <brrt> i see

[15:16] <brrt> that makes a bunch of sense

[15:18] <jnthn> It's also important that the write does not take place if the guard isn't met :)

[15:18] <jnthn> (Yes, I did that mistake. Yes, it was fun to debug. :P)

[15:18] <MasterDuke> btw, while people are active. did it make sense in https://github.com/MoarVM/MoarVM/pull/949 to merge my branch into post-release-opts? or should i have just done master?

[15:18] <timotimo> post-release-opts is safe in any case

[15:21] <jnthn> It's safe, though its merge schedule is unknown

[15:23] <MasterDuke> well, no hurry for my PR

[15:33] *** brrt left
[15:36] *** fake_space_whale joined
[15:37] *** p6bannerbot sets mode: +v fake_space_whale

[15:46] *** avar left
[15:47] *** avar joined
[15:47] *** avar left
[15:47] *** avar joined
[15:47] *** p6bannerbot sets mode: +v avar

[15:48] *** p6bannerbot sets mode: +v avar

[16:02] *** robertle joined
[16:03] *** p6bannerbot sets mode: +v robertle

[16:06] *** brrt joined
[16:07] *** p6bannerbot sets mode: +v brrt

[16:10] *** stmuk_ joined
[16:11] *** p6bannerbot sets mode: +v stmuk_

[16:12] *** stmuk left
[16:20] *** zakharyas joined
[16:21] *** p6bannerbot sets mode: +v zakharyas

[16:31] *** brrt left
[16:34] *** fake_space_whale left
[16:42] *** zakharyas left
[16:56] * timotimo has been writing a blog post about optimizing the performance of a given piece of code, based on the FASTA parsing task off stackoverflow

[16:56] <timotimo> but now i'm AFK for a while

[16:56] <timotimo> i'd say it's about 1/3rd done, at 822 words so far

[17:01] <samcv> AlexDaniel: hopefully soon. i finally have actual time. was a family thing for a few days and had no time, but now i do

[17:01] <AlexDaniel> cool

[18:29] *** domidumont joined
[18:30] *** p6bannerbot sets mode: +v domidumont

[18:30] *** zakharyas joined
[18:30] *** p6bannerbot sets mode: +v zakharyas

[18:48] <Geth> ¦ MoarVM: bdf961d5fc | (Samantha McVey)++ | tools/update-changelog.p6

[18:48] <Geth> ¦ MoarVM: Add many more features to update-changelog.p6

[18:48] <Geth> ¦ MoarVM:

[18:48] <Geth> ¦ MoarVM: Allow viewing all changes done so far, allow changing view options. Add

[18:48] <Geth> ¦ MoarVM: a few tests and fix a bug in auto categorizing some commits based on

[18:48] <Geth> ¦ MoarVM: directory name.

[18:48] <Geth> ¦ MoarVM:

[18:48] <Geth> ¦ MoarVM: Use rlwrap if it exists to allow easily editing commit subject's with

[18:48] <Geth> ¦ MoarVM: preentered text of what it was previously.

[18:48] <Geth> ¦ MoarVM: review: https://github.com/MoarVM/MoarVM/commit/bdf961d5fc

[18:48] <Geth> ¦ MoarVM: 0b34ce5e23 | (Samantha McVey)++ | tools/update-changelog.p6

[18:48] <Geth> ¦ MoarVM: Add goto specific commit and print uncomplete entries to update-changelog

[18:48] <Geth> ¦ MoarVM: review: https://github.com/MoarVM/MoarVM/commit/0b34ce5e23

[18:49] <samcv> i have 14 options but i still don't have enough

[18:49] <samcv> MODIFY (e)dit/(d)rop/(c)ategory/d(o)ne/(T)itlecase; PRINT (b)ody/d(i)ff/num-(l)eft/(C)omplete/(U)uncomplete; GOTO (n)ext/(G)oto commit ID; (Q)uit and save or (s)ave:

[19:05] *** zakharyas left
[19:08] *** travis-ci joined
[19:08] *** p6bannerbot sets mode: +v travis-ci

[19:08] <travis-ci> MoarVM build failed. Samantha McVey 'Add goto specific commit and print uncomplete entries to update-changelog'

[19:08] <travis-ci> https://travis-ci.org/MoarVM/MoarVM/builds/421708094 https://github.com/MoarVM/MoarVM/compare/5bfad12bbcef...0b34ce5e23e7

[19:08] *** travis-ci left
[19:09] *** domidumont left
[19:56] *** lizmat joined
[19:57] *** p6bannerbot sets mode: +v lizmat

[20:38] *** brrt joined
[20:38] *** p6bannerbot sets mode: +v brrt

[20:57] <samcv> ok at 176 more changelog entries. time for a short break

[20:58] <samcv> this tool is making it much faster to go through the changelog :) and i can merge one commit's subject into another one. though that needs a bit more refinement. and i probably will also add ability to tag items that i need to ask people about

[21:33] *** lizmat left
[21:44] *** brrt left
[21:44] *** robertle left
[22:03] *** Kaypie joined
[22:03] *** Kaiepi left
[22:03] *** p6bannerbot sets mode: +v Kaypie

[23:04] <japhb> samcv++  # Making tools to make the job easier