Perl 6 - the future is here, just unevenly distributed

IRC log for #moarvm, 2017-05-15

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:14 colomon joined #moarvm
00:15 lizmat joined #moarvm
00:24 colomon joined #moarvm
00:47 colomon_ joined #moarvm
01:49 ilbot3 joined #moarvm
01:49 Topic for #moarvm is now https://github.com/moarvm/moarvm | IRC logs at  http://irclog.perlgeek.de/moarvm/today
03:01 vendethiel joined #moarvm
05:25 domidumont joined #moarvm
05:30 domidumont joined #moarvm
06:01 domidumont joined #moarvm
06:13 vendethiel- joined #moarvm
07:24 lizmat joined #moarvm
07:36 zakharyas joined #moarvm
07:49 domidumont joined #moarvm
07:50 brrt joined #moarvm
07:52 domidumont joined #moarvm
07:56 brrt joined #moarvm
08:27 robertle joined #moarvm
08:28 brrt good * #moarvm
08:39 domidumont joined #moarvm
08:43 jnthn morning o/
08:43 yoleaux 14 May 2017 21:24Z <MasterDuke_> jnthn: do you have an opinion re https://rt.perl.org/rt3/Public/Bug/Display.html?id=131310 ? should subsets of native types be allowed?
09:02 domidumont joined #moarvm
09:04 jnthn .tell MasterDuke_ It'll probably be tricky to make them work in the general case (think native arrays, for example; I'm not immediately sure how we'd make them work in that case). I suspect getting them correct even on simple variables will be a bit tricky. So, maybe some day, but it won't be entirely easy.
09:04 yoleaux jnthn: I'll pass your message to MasterDuke_.
09:04 brrt \o jnthn
09:05 jnthn o/ brrt
09:06 brrt i think i know where my bug is
09:06 brrt you are not expected to know what bug i'm talking about, since i haven't quite explained it
09:07 jnthn This isn't the heap one still, I presume? :-)
09:08 brrt no, that's been fixed
09:08 brrt but the tl;dr, decont is givng me considerable problems because it is invokish
09:08 brrt and the invokish guard requires two registers, and we only have one scratch register
09:09 brrt and the upshot is that i think now that i've requested a register to be allocated, then the arglist / call required register resolution doesn't quite work right
09:10 brrt and that may be caused because … ugh
09:10 brrt it's complicated
09:10 brrt well, there may be two causes
09:10 brrt a): the resolution logic is just wrong
09:12 brrt b): the resolution logic is correct, but it doesn't take into consideration the possibility that the live range for the CALL registe rhas been spilled
09:12 brrt b): has a simple resolution
09:12 brrt but i first would need to confirm it
09:13 brrt ultimately it manifest as overwriting the register that is supposed to handle the object on which we call the fetch() pointer
09:16 jnthn Oops.
09:39 domidumont joined #moarvm
09:42 domidumont joined #moarvm
10:10 brrt yeah
10:10 brrt the trick is figuring out how
11:26 domidumont1 joined #moarvm
11:32 brrt joined #moarvm
11:33 brrt joined #moarvm
12:00 domidumont joined #moarvm
12:02 domidumont joined #moarvm
12:32 domidumont joined #moarvm
12:36 domidumont1 joined #moarvm
15:31 AlexDaniel joined #moarvm
15:49 AlexDaniel joined #moarvm
16:09 brrt joined #moarvm
16:21 lizmat joined #moarvm
16:31 domidumont joined #moarvm
16:32 vendethiel joined #moarvm
17:41 praisethemoon joined #moarvm
17:41 praisethemoon joined #moarvm
17:50 robertle joined #moarvm
17:56 AlexDaniel joined #moarvm
18:49 lizmat joined #moarvm
19:05 colomon joined #moarvm
19:07 lizmat joined #moarvm
19:20 lizmat joined #moarvm
19:59 Ven joined #moarvm
20:01 lizmat_ joined #moarvm
20:05 Ven_ joined #moarvm
20:11 Ven_ joined #moarvm
20:36 Ven joined #moarvm
20:41 Ven_ joined #moarvm
20:47 Ven_ joined #moarvm
20:49 lizmat_ joined #moarvm
21:00 lizmat joined #moarvm
21:20 lizmat joined #moarvm
21:55 SourceBaby joined #moarvm
22:45 TimToady joined #moarvm

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary