github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm Set by AlexDaniel on 12 June 2018. |
|||
00:04
Ven`` left
00:55
lizmat left
01:00
lizmat joined,
p6bannerbot sets mode: +v lizmat
02:59
lizmat left
03:01
MasterDuke joined
03:02
p6bannerbot sets mode: +v MasterDuke
03:17
MasterDuke left
03:20
leont left
|
|||
samcv | it looks like libtommath is likely to go BSD/MIT license github.com/libtom/libtommath/issues/126 | 03:54 | |
07:07
domidumont joined
07:08
p6bannerbot sets mode: +v domidumont
07:35
robertle joined,
p6bannerbot sets mode: +v robertle
08:43
lizmat joined,
p6bannerbot sets mode: +v lizmat
09:14
zakharyas joined
09:15
p6bannerbot sets mode: +v zakharyas
09:32
robertle left
10:52
lizmat left
11:16
domidumont left
12:06
leont joined
12:07
p6bannerbot sets mode: +v leont
12:21
leont left
12:25
zakharyas left
12:40
domidumont joined,
domidumont left
12:57
domidumont joined
12:58
p6bannerbot sets mode: +v domidumont
13:37
brrt joined
13:38
p6bannerbot sets mode: +v brrt
|
|||
brrt | \o | 13:59 | |
yoleaux | 22 Nov 2018 02:17Z <kiwi_95> brrt: (and jnthn) I'd love to read your take on "join points" and "basic blocks with arguments" as discussed here www.reddit.com/r/ProgrammingLangua...lift_uses/ | ||
brrt | .tell kiwi_95 - I'm honestly not personally sufficiently advanced that I could tell you what the difference really is | 14:00 | |
yoleaux | brrt: I'll pass your message to kiwi_95. | ||
brrt | in practical terms. It seems pretty equivalent to me | ||
14:01
zakharyas joined
14:02
p6bannerbot sets mode: +v zakharyas
|
|||
brrt | .ask nine I wonder if you can help me make a test case for nativecallinvoke, and maybe start thinking about deprecating the difference between nativeinvoke, nativeclallinvoke and plain invoke | 14:02 | |
yoleaux | brrt: I'll pass your message to nine. | ||
14:12
domidumont left
14:27
leont joined
14:28
p6bannerbot sets mode: +v leont
|
|||
Geth | MoarVM/pea: 913504df90 | (Jonathan Worthington)++ | 8 files Preparations for deopt materialization * Stub in the data structures we'll use to describe materializations of replaced objects and what deopt points need them * Add an NYI panic in deopt in the case that we encounter something to materialize (should never trigger at the moment) |
15:54 | |
15:58
avar left
16:00
avar joined,
avar left,
avar joined,
p6bannerbot sets mode: +v avar
16:01
p6bannerbot sets mode: +v avar
|
|||
brrt | ohai jnthn | 16:05 | |
jnthn | o/ brrt | 16:08 | |
This is heavy stuff for a Friday... :) | 16:14 | ||
17:02
zakharyas left
17:05
brrt left
|
|||
Geth | MoarVM/pea: 6e28e173bd | (Jonathan Worthington)++ | src/spesh/pea.h Target register goes with deopt point Since we might have to materialize *one* object, but put it into *many* registers during deopt, for example because of aliasing. |
17:18 | |
MoarVM/pea: d29dd72e77 | (Jonathan Worthington)++ | src/spesh/dump.c Dump materialization data |
|||
MoarVM/pea: ad480447f5 | (Jonathan Worthington)++ | src/spesh/pea.c Keep a set of tracked registers These will be needed in order to properly consider deopt points, and see if we need to save materialization information. |
17:22 | ||
MoarVM/pea: e317922036 | (Jonathan Worthington)++ | 2 files Sketch out creating deopt/materialization info |
|||
jnthn | Well, it's some progress... bbl | 17:27 | |
18:38
zakharyas joined,
p6bannerbot sets mode: +v zakharyas
19:12
zakharyas left
|
|||
nine | ~~ | 19:18 | |
yoleaux | 14:02Z <brrt> nine: I wonder if you can help me make a test case for nativecallinvoke, and maybe start thinking about deprecating the difference between nativeinvoke, nativeclallinvoke and plain invoke | ||
nine | .tell brrt I sure hope I can help :) | ||
yoleaux | nine: I'll pass your message to brrt. | ||
20:23
Ven`` joined
20:24
p6bannerbot sets mode: +v Ven``,
Ven` joined
20:25
p6bannerbot sets mode: +v Ven`
20:28
Ven`` left
21:19
Ven` left
21:44
patrickb joined,
p6bannerbot sets mode: +v patrickb
23:32
patrickb left
23:40
lizmat joined,
p6bannerbot sets mode: +v lizmat
|