brrt good * #moarvm 08:28
jnthn morning o/ 08:43
yoleaux 14 May 2017 21:24Z <MasterDuke_> jnthn: do you have an opinion re rt.perl.org/rt3/Public/Bug/Display...?id=131310 ? should subsets of native types be allowed?
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_.
brrt \o jnthn
jnthn o/ brrt 09:05
brrt i think i know where my bug is 09:06
you are not expected to know what bug i'm talking about, since i haven't quite explained it
jnthn This isn't the heap one still, I presume? :-) 09:07
brrt no, that's been fixed 09:08
but the tl;dr, decont is givng me considerable problems because it is invokish
and the invokish guard requires two registers, and we only have one scratch register
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:09
and that may be caused because … ugh 09:10
it's complicated
well, there may be two causes
a): the resolution logic is just wrong
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
b): has a simple resolution
but i first would need to confirm it
ultimately it manifest as overwriting the register that is supposed to handle the object on which we call the fetch() pointer 09:13
jnthn Oops. 09:16
brrt yeah 10:10
the trick is figuring out how

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!