brrt good * #moarvm 06:43
nwc10 good *, brrt 07:18
brrt good * nwc10 07:20
have you also seen the blowup of CORE.setting recently?
nwc10 blowup in what sense? It still works (builds) for me, but I didn't notice if it needs more time or more RAM 07:23
brrt as in, ASAN crashes 07:56
nwc10 ASAN on "my" machine doesn't crash on it 08:04
brrt hmmm 08:08
what architecture is that
nwc10 x86_64 GNU/Linux
nwc10 goes to replace "emperor's new cup of coffee" with something a bit less vapourware 08:16
lizmat S01-perl-5-integration/basic.t is reliably segfaulting for me now 14:58
brrt yay 15:07
have you tried to point jit-bisect —spesh at that
or just jit-bisect.pl (for the expr jit)
lizmat MVM_JIT_EXPR_DISABLE=1 is the env var, right ? 15:08
to switch off expr jit ? 15:09
brrt yeah
but jit-bisect.pl will do that automatically for you
lizmat it also segfaults with MVM_JIT_EXPR_DISABLE=1 , but not as often 15:10
could it be that it doesn't make a difference between MVM_JIT_EXPR_DISABLE=1 and MVM_JIT_EXPR_DISABLE=0 ? 15:11
brrt yes :-D 15:18
oh, you mean, running jit-bisect.pl
yeah, that will clear out any such flags prior to running
AlexDaniel samcv: created an issue for it anyway: github.com/MoarVM/MoarVM/issues/764 18:56
samcv AlexDaniel: have the fix ready 23:00
Geth MoarVM: c749da122c | (Samantha McVey)++ | tools/ucd2c.pl
ucd2c.pl: Explicitly set default values for several properties

Also, set the default values for name, gencat_name and General_Category for codepoints not in UnicodeData.txt.
23:02
MoarVM: 65fa583822 | (Samantha McVey)++ | tools/ucd2c.pl
ucd2c.pl: Rename int and str enum variables to indicate their use

This makes it much easier to tell which property is being added to, the switch for MVM_unicode_get_property_int or MVM_unicode_get_property_str.
MoarVM: 34d01a811e | (Samantha McVey)++ | 2 files
Fix the Unicode database from adding int properties to str function

This was causing a compiler warning because of the type difference. We shouldn't be requesting, or at least should expect to get an empty string if we query an int property using the getuniprop_str op so there should be no difference in Perl6 functionality since it only requests using getuniprop_int.
Fixes issue #764