github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
ugexe darwin,linux: more conservative minimum stack size -- github.com/libuv/libuv/commit/d89b...b94e18b904 01:33
brrt \o 08:54
I've gotten the floating point support so far as a segfault
So that's progress
:-D
jnthn Congrats or something :) 08:59
yoleaux 00:37Z <vrurg> jnthn: If'm getting right your complaint about NQP in detached head, then the solution would be to use --gen-nqp=master
01:22Z <vrurg> jnthn: Got the problem reproduced, will have it fixed Monday.
Geth MoarVM: cce71cdbf5 | (Timo Paulssen)++ | src/jit/graph.c
Revert "JIT Devirtualize slice (and the create it implies)"

This reverts commit afd8f93706c346f28f6eb98baeb416d6c7fc183b.
It wasn't actually correct. Just not 100% sure in what way it is wrong. Will later rebuild this commit from scratch.		 11:05
brrt \o 17:53
pamplemousse o/ 18:04
brrt good afternoon 18:06
google tells me we have very similar weather today
yay, bug fixed 18:07
I decided to make the register allocator mostly oblivious to the type of register
and to have the emitter figure it out 18:09
brrt the emitter, after all, can assume it knows all about the target architecture, since it must by definition 18:09
brrt pamplemousse: your network is less than reliably connected 18:15
pamplemousse brrt: It's definitely less than ideal 18:16
Geth MoarVM/jit-expr-float: 19 commits pushed by (Bart Wiegmans)++
review: github.com/MoarVM/MoarVM/compare/9...64fe72773b
brrt how come? 18:17
pamplemousse I think my wireless card doesn't work very well with the available wireless access point 18:25
brrt it's been a long time since I worried about those things 18:28
Geth MoarVM/jit-expr-float: 3055659d1e | (Bart Wiegmans)++ | 6 files
[JIT] Handle floating point registers better

  - check for MVM_JIT_STORAGE_GPR in a few places
  - expect the emitter to figure out the register class for a
   register (otherwise, we have to maintain that throughout the
   compiler, and it's redundant)
  - use the correct spare register for operator argument order
   resolution		 18:43
brrt typechecking hates me 19:25
lizmat
.oO( you don't look like that to me :-)
 19:39
brrt but this is typechecking, of my own design 19:48
lizmat and another Perl 6 Weekly hits the Net: p6weekly.wordpress.com/2019/06/10/...te-course/ 19:49
brrt lizmat++ 19:50
hey, I hadn't seen pamplemousse++ 's last blog post 20:05
pamplemousse I'm working on another one covering my progress this past week that should be up in a day or two 20:09
brrt cool!
tadzik awesome :) 20:11
jnthn lizmat++ # weekly 21:01
yoleaux 13:42Z <vrurg> jnthn: not sure you'd have time to reply this week. In short about the subsets: their current behavior is a bug. It's not like breaking backward compat just for the sake of a new feature.
timotimo we used to have a server for perl6 devs where they could run an instance of irssi or weechat (though no reason not to allow a traditional bouncer, or a quassel core or what ever else) so that they don't have to worry about getting disconnected from irc 22:44
but then that machine turned into a very unhealthy snack
timotimo hm, i suppose it would already have been unhealthy to snack on that machine before it broke 22:50
timotimo redzones between an object's header and its body when --valgrind is on, yea or nay? 23:20
japhb Heatwave outside: 40+C. Office w/ broken A/C: 30+C. Home office: 20C. Aaahhhhh .... 23:22
timotimo yikes 23:23
jnthn We just got a nice bit of rain, and the air is fresher now, at least :) 23:27
Going to Scandinavia for the next ~week, which should be cooler :) 23:28

Powered by Cro and the Raku® Programming Language.

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

Thank you!