|
github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm Set by AlexDaniel on 12 June 2018. |
|||
|
00:54
MasterDuke joined,
p6bannerbot sets mode: +v MasterDuke,
MasterDuke left,
MasterDuke joined,
herbert.freenode.net sets mode: +v MasterDuke,
p6bannerbot sets mode: +v MasterDuke
03:17
MasterDuke left
03:23
Ven`` joined
03:24
p6bannerbot sets mode: +v Ven``
03:34
Ven`` left
08:57
domidumont joined
08:58
p6bannerbot sets mode: +v domidumont
12:48
lucasb joined,
p6bannerbot sets mode: +v lucasb
13:16
MasterDuke joined,
p6bannerbot sets mode: +v MasterDuke,
MasterDuke left,
MasterDuke joined,
herbert.freenode.net sets mode: +v MasterDuke,
p6bannerbot sets mode: +v MasterDuke
13:54
Ven`` joined
13:55
p6bannerbot sets mode: +v Ven``
|
|||
| Geth | MoarVM: c5bc342e3d | (Stefan Seifert)++ | src/spesh/optimize.c Fix rakudo build failure on big endian architectures On big endian machines, we optimized istrue/isfalse to 0 all the time since the least significant bit of lit_i64 is outside the lit_i16 that will be read by the const_i64_16 op. All other optimizations that write a constant seem to correctly write to lit_16. Fix GH #2563 |
14:29 | |
| MasterDuke | nine++ | 14:33 | |
|
14:49
AlexDani` joined
14:50
p6bannerbot sets mode: +v AlexDani`
14:55
zakharyas joined,
p6bannerbot sets mode: +v zakharyas
|
|||
| dogbert11 | nine++, is it possible that the other blockers were suffering from the same problem? | 15:03 | |
| nine | dogbert11: github.com/rakudo/rakudo/issues/2567 and github.com/rakudo/rakudo/issues/2564 were both reported on little endian machines, so this bug cannot be the cause | 16:24 | |
|
16:35
AlexDani` is now known as AlexDaniel
18:18
Kaiepi joined,
p6bannerbot sets mode: +v Kaiepi
18:30
lizmat joined,
p6bannerbot sets mode: +v lizmat
18:34
Kaiepi left
19:27
Ven`` left
19:46
domidumont left
19:51
Ven`` joined
19:52
p6bannerbot sets mode: +v Ven``
19:56
MasterDuke left
20:09
zakharyas left
20:48
lucasb left
21:12
Ven`` left
21:13
Ven`` joined
21:14
p6bannerbot sets mode: +v Ven``
21:20
zakharyas joined
21:21
p6bannerbot sets mode: +v zakharyas
|
|||
| robertle | nine: awesome stuff, I have two questions: a) do you think that the fix to #2563 could be alied on top of 2018.12 alone, or does it require other changes before it? | 21:26 | |
| b) does this require a rebuild of nqp? | 21:27 | ||
| timotimo | if you're refering to the commit last pushed to moar by nine, it should totally apply cleanly to 2018.12 and earlier, and not need any other changes. nqp would not need to be rebuilt | 21:39 | |
| robertle | fab | 21:40 | |
|
22:26
zakharyas left
|
|||
| jnthn | nine++ # fixing the spesh BE issue | 22:38 | |
| robertle | yeah, I can only imagine how much time has gone into this two-character fix :) | 22:42 | |
| nine | Good thing I'm not payed by character then ;) | 22:52 | |
|
22:58
Ven`` left
22:59
Ven`` joined
23:00
p6bannerbot sets mode: +v Ven``
|
|||