Perl 6 - the future is here, just unevenly distributed

IRC log for #moarvm, 2017-12-12

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

All times shown according to UTC.

Time Nick Message
00:00 committable6 joined #moarvm
00:00 unicodable6 joined #moarvm
00:00 greppable6 joined #moarvm
00:00 bisectable6 joined #moarvm
02:57 ilbot3 joined #moarvm
02:57 Topic for #moarvm is now https://github.com/moarvm/moarvm | IRC logs at  http://irclog.perlgeek.de/moarvm/today
03:23 lizmat joined #moarvm
05:12 committable6 joined #moarvm
06:04 releasable6 joined #moarvm
06:37 domidumont joined #moarvm
07:03 domidumont joined #moarvm
07:12 domidumont joined #moarvm
07:20 brrt joined #moarvm
07:35 reportable6 joined #moarvm
07:36 brrt ohai #moarvm
07:37 nwc10 good *, brrt
07:38 brrt i'm looking for the piece of code that made the linear scan allocator blow up
07:39 brrt i've decided that using && to force control flow between two assignment statements is a bit too much
07:39 brrt it was something like perl6-valdgrind-m -e 'my @a[1,<1>] for ^100000'
07:39 brrt should've made that a test case
07:47 brrt hmm, i have a valgrind blowup in building CORE.setting
07:57 brrt and os x locks up of course
08:17 Ven`` joined #moarvm
08:47 lizmat m: my @matrix[2;2] = [1,2],[3,4]; @matrix[<0>;0] for ^1000000
08:47 camelia rakudo-moar 9fd5042b8: ( no output )
08:47 lizmat m: my @matrix[2;2] = [1,2],[3,4]; @matrix[<0>;0] for ^1000000
08:47 camelia rakudo-moar 9fd5042b8: ( no output )
08:47 lizmat m: my @matrix[2;2] = [1,2],[3,4]; @matrix[<0>;0] for ^1000000
08:47 camelia rakudo-moar 9fd5042b8: OUTPUT: «(signal SEGV)»
08:47 lizmat m: my @matrix[2;2] = [1,2],[3,4]; @matrix[<0>;0] for ^1000000
08:47 camelia rakudo-moar 9fd5042b8: ( no output )
08:47 lizmat that'd be the one, I guess  :-)
08:47 lizmat needs to be a shaped array
08:47 lizmat .tell brrt my @matrix[2;2] = [1,2],[3,4]; @matrix[<0>;0] for ^1000000
08:47 yoleaux lizmat: I'll pass your message to brrt.
09:00 jsimonet joined #moarvm
09:00 brrt joined #moarvm
09:18 robertle joined #moarvm
09:21 geospeck joined #moarvm
13:23 unicodable6 joined #moarvm
13:42 dogbert2 joined #moarvm
14:34 zakharyas joined #moarvm
15:13 zakharyas joined #moarvm
15:56 zakharyas joined #moarvm
16:01 ggoebel joined #moarvm
16:06 brrt joined #moarvm
16:28 brrt i'm trying to bisect the issue but valgrind keeps getting stuck
16:28 yoleaux 08:47Z <lizmat> brrt: my @matrix[2;2] = [1,2],[3,4]; @matrix[<0>;0] for ^1000000
16:28 brrt thanks lizmat
16:56 zakharyas joined #moarvm
17:02 domidumont joined #moarvm
17:04 domidumont joined #moarvm
17:06 zakharyas joined #moarvm
17:21 lizmat joined #moarvm
17:31 nwc10 joined #moarvm
17:34 geospeck joined #moarvm
17:40 zakharyas joined #moarvm
17:42 timotimo i think there's probably no damage in just merging CStructArray - maybe after the next release - and let people have at it and then fix any bugs that remain
17:48 evalable6 joined #moarvm
18:22 zakharyas joined #moarvm
18:31 geospeck joined #moarvm
18:53 Ven`` joined #moarvm
19:14 Ven`` joined #moarvm
19:25 Ven`` joined #moarvm
20:12 ggoebel joined #moarvm
20:33 benchable6 joined #moarvm
20:35 Ven`` joined #moarvm
20:37 Util joined #moarvm
20:37 geospeck joined #moarvm
20:40 samcv joined #moarvm
20:40 Voldenet joined #moarvm
20:40 Voldenet joined #moarvm
20:45 BinGOs joined #moarvm
20:48 ggoebel joined #moarvm
20:54 colomon joined #moarvm
20:59 benchable6 joined #moarvm
21:00 bisectable6 joined #moarvm
21:00 greppable6 joined #moarvm
21:00 reportable6 joined #moarvm
21:00 evalable6 joined #moarvm
21:00 unicodable6 joined #moarvm
21:59 Ven`` joined #moarvm
22:16 squashable6 joined #moarvm
22:18 Ven`` joined #moarvm
22:31 colomon_ joined #moarvm
22:43 Ven`` joined #moarvm
23:07 colomon joined #moarvm
23:27 colomon joined #moarvm
23:27 lizmat joined #moarvm

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