brrt good * #moarvm 08:21
timotimo yo brrt 09:13
brrt \o timotimo 09:14
i'm reasonably confident that a bitmap is the right choice for my set-of-live-ranges-per-block
timotimo so for each block you'll have as many bits as there are ranges? 09:16
brrt yes 09:18
so with 64 bit pointers, or 32 bit keys, you're going to need a pretty large number of live ranges and a pretty low 'fill' per block to beat the memory usage of the bitmap 09:21
and in terms of compuation efficiency it's no contest
timotimo mhm 09:22
Geth MoarVM: 3e4ed6bffe | (Samantha McVey)++ | src/strings/ops.c
Add can_fit_into_8bit funct, put logic used many places into one funct

There are 7 places we use checks for this within src/strings/ops.c Writing out the conditionals which sometimes use || and sometimes use &&. They also sometimes use >= sign and other times > signs. Make it more consistent for ease of reading and clarity.		 10:37
MoarVM: 957759c84b | (Samantha McVey)++ (committed using GitHub Web editor) | src/strings/ops.c
Merge pull request #591 from samcv/master

Add can_fit_into_8bit funct, put logic used many places into one funct
jnthn Nice. From scratch MoarVM build on my new machine is 8s. :) 14:51
And spectest in 106s 14:59
With TEST_JOBS=16
TEST_JOBS=20 shaves a few more seconds off, but not much 15:01
Though with that a make test of Rakudo (with NativeCall already being precomp'd) takes 2s 15:02
Heh, with --jobs=20 I can get NQP to spectest in 2s also 15:03
(hardware improvements)++ :)
MasterDuke_ nice. what is the new hardware? 15:27
jnthn Has a Xeon 6-core (12 virtual) CPU, 32 GB RAM and a fast SSD :) 15:30
dogbert17 congrats, nice HW
MasterDuke_ nice. i've gotten kind of spoiled by 20-core (40 virtual) xeons at work and have thought about going the xeon route at home 15:33
dogbert17 I thought you're looking into AMD as well
MasterDuke_ but nine's numbers on his new ryzen are also pretty good, and that's a much cheaper option

Powered by Cro and the Raku® Programming Language.

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

Thank you!