|
github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm Set by AlexDaniel on 12 June 2018. |
|||
|
00:00
lizmat joined,
p6bannerbot sets mode: +v lizmat
00:23
fake_space_whale left
00:24
MasterDuke joined,
p6bannerbot sets mode: +v MasterDuke,
MasterDuke left,
MasterDuke joined,
herbert.freenode.net sets mode: +v MasterDuke,
p6bannerbot sets mode: +v MasterDuke
00:47
Kaiepi left
00:48
Kaiepi joined
00:49
p6bannerbot sets mode: +v Kaiepi
|
|||
| MasterDuke | jnthn, samcv, etc: forums.swift.org/t/string-s-abi-and-utf-8/17676 some interesting info about changes to how swift handles string | 02:44 | |
|
03:32
MasterDuke left
|
|||
| samcv | thanks, will check it out | 03:55 | |
|
04:02
colomon joined,
colomon left
06:12
lizmat left
06:53
domidumont joined
06:54
p6bannerbot sets mode: +v domidumont
07:31
robertle joined
07:32
p6bannerbot sets mode: +v robertle
08:07
domidumont left,
domidumont joined
08:08
p6bannerbot sets mode: +v domidumont
08:35
zakharyas joined
08:36
p6bannerbot sets mode: +v zakharyas
08:43
lizmat joined,
p6bannerbot sets mode: +v lizmat
|
|||
| nwc10 | They write of UTF-8 (particularly in reverse) "But, this isn’t really an issue: on modern CPUs this increase in encoding complexity is more than offset by the decrease in model complexity by having a unified storage representation." | 09:17 | |
| but I wonder how much of that "faster" is comparision with "ASCII or UTF-16" (where the latter is still variable width) | 09:18 | ||
| and how much their benchmarks (and use cases) are about linearly acessing strings, not index-based lookups which I *think* are needed by regex engines | |||
|
09:34
robertle left
09:36
robertle joined
09:37
p6bannerbot sets mode: +v robertle
09:46
robertle left
09:49
robertle joined
09:50
p6bannerbot sets mode: +v robertle
|
|||
| nine | Why is the information about which of an op's arguments need to be deconted an argument to the add_core_moarop_mapping method? It's a static property of the op. Wouldn't that belong in oplist instead? Same for $ret which is information about which argument will be written to. | 10:30 | |
| And an even more heretical question: why do we type registers? In memory, a register can hold anything. It's really the interpretation by the ops that turns anything into something. So why can't we have a register holding an int and later on an object when it's not needed anymore for the int? | 11:18 | ||
|
12:16
zakharyas left
|
|||
| timotimo | because the GC has to go through a frame and add only object and string registers to worklists | 12:38 | |
| otherwise an integer or num will cause segfaults if it lives in an object or string register | |||
| and which arguments want to have a decont applied to them is, to me, more an nqp language thing | 12:39 | ||
| nine | Ah, ok, the GC explains that of course. | 12:47 | |
| The point of the decont question is really: if we move that information to oplist, I can generate better tailored code for qast to mbc compilation of every op that goes through moarop_mapper | 12:49 | ||
| timotimo | interesting | 12:50 | |
| nine | A different approach would be to generate and compile a QAST tree for those mapper functions instead of having update_ops.pl6 generate the source code | ||
|
13:42
zakharyas joined
13:43
p6bannerbot sets mode: +v zakharyas
14:37
domidumont left
14:53
domidumont joined,
p6bannerbot sets mode: +v domidumont
15:18
domidumont1 joined
15:19
p6bannerbot sets mode: +v domidumont1
15:21
domidumont left
16:15
fake_space_whale joined
16:16
p6bannerbot sets mode: +v fake_space_whale
16:36
fake_space_whale left
16:48
fake_space_whale joined
16:49
p6bannerbot sets mode: +v fake_space_whale
17:02
robertle left
|
|||
| timotimo | do we perhaps want an attribute trait "is not_serialized" so that we can make an NFA's list version of itself turn to null when it's deserialized? | 17:18 | |
| statelist* | 17:19 | ||
| not for end users, of course | |||
| it's an exquisite footgun for sure | 17:21 | ||
| dogbert11 | Bytecode validation error at offset 74, instruction 13: operand type 48 does not match register type 160 # hmm | 17:33 | |
| when trying to build nqp b8ecfa43. Building newer versions lead to the entire build process hanging (on 32 bit). | 17:34 | ||
| timotimo | the last time someone had something like that, something like nuking the install folder helped | 17:36 | |
|
18:05
zakharyas left
18:07
zakharyas joined
18:08
p6bannerbot sets mode: +v zakharyas
18:24
robertle joined
18:25
p6bannerbot sets mode: +v robertle
18:40
domidumont1 left
18:50
zakharyas left
19:44
fake_space_whale left
20:14
zakharyas joined,
p6bannerbot sets mode: +v zakharyas
20:47
SmokeMachine left
20:48
SmokeMachine joined,
p6bannerbot sets mode: +v SmokeMachine,
chansen___ left
20:50
chansen___ joined,
p6bannerbot sets mode: +v chansen___
21:08
TimToady left
21:16
TimToady joined,
p6bannerbot sets mode: +v TimToady
22:01
zakharyas left
22:05
robertle left
|
|||