|
Welcome to the main channel on the development of MoarVM, a virtual machine for NQP and Rakudo (moarvm.org). This channel is being logged for historical purposes. Set by lizmat on 24 May 2021. |
|||
|
00:00
reportable6 left
00:01
reportable6 joined
00:16
discord-raku-bot left
00:17
discord-raku-bot joined
01:16
discord-raku-bot left
01:17
discord-raku-bot joined
02:17
discord-raku-bot left,
discord-raku-bot joined
02:23
epony joined
03:17
discord-raku-bot left,
discord-raku-bot joined
05:18
linkable6 left,
evalable6 left
05:19
evalable6 joined
05:20
linkable6 joined
06:00
reportable6 left
06:01
reportable6 joined
07:07
samcv_ joined,
Voldenet_ joined
07:14
JRaspass left,
samcv left,
Voldenet left,
Voldenet_ is now known as Voldenet
07:22
JRaspass joined
07:39
epony left
08:17
discord-raku-bot left,
discord-raku-bot joined
08:44
sena_kun joined
09:55
evalable6 left
09:57
evalable6 joined
10:35
epony joined
11:49
discord-raku-bot left,
discord-raku-bot joined
11:57
discord-raku-bot left
11:58
discord-raku-bot joined
12:00
reportable6 left
12:03
reportable6 joined
13:53
dogbert11 left
13:57
dogbert11 joined
14:17
discord-raku-bot left
14:18
discord-raku-bot joined
14:30
dogbert11 left
14:50
dogbert11 joined
15:06
discord-raku-bot left,
discord-raku-bot joined
16:02
dogbert17 joined
16:04
dogbert11 left
16:40
discord-raku-bot left,
discord-raku-bot joined
17:17
discord-raku-bot left,
discord-raku-bot joined
17:35
linkable6 left
17:38
linkable6 joined
18:00
reportable6 left
18:02
raku-discord joined,
reportable6 joined,
raku-discord left
18:11
squashable6 left
18:12
squashable6 joined
19:47
discord-raku-bot left
19:53
raku-discord joined
|
|||
| timo | who wants to check out if in theory starting to validate a frame mentioned in a frame we're currently validating in a separate thread can make stuff faster or is mostly wasted effotr | 20:00 | |
| i feel like digging out and refreshing the tracery stuff can give a good look at the timeline there | |||
| maybe checking how often a frame mentioned in another frame is validated very soon thereafter is a good starting point, then looking if there's a cheap way during validation to see if something is likely to be hit based on previous (or maybe following) instructions, like in order to identify stuff happening in rarely taken error branches | 20:03 | ||
|
20:13
raku-discord left,
discord-raku-bot joined
|
|||
| timo | alternatively, how much would it be worth to have a hand-crafted or at-build-time-measured-and-injected list of frames that we always run through when rakudo starts | 20:20 | |
|
20:21
squashable6 left
20:22
squashable6 joined
|
|||
| timo | i'm still working off the fact that during 3.37% of the main thread's time for an empty program the MVM_validate_static_frame, though what i remembered was 5%, which is actually in prepare_and_validate_static_frame, haven't looked what the difference is | 20:23 | |
| prepare_and_verify_static_frame* | 20:25 | ||
| prepare_and_verify_static_frame assumes we hold the CU deserialize frame mutex, which sounds like it needs resolved if we want to validate two things at the same time | 20:30 | ||
|
20:58
sena_kun left
21:07
Geth left,
Geth joined,
Geth left
21:08
Geth joined
22:07
Geth left
22:08
Geth joined
22:12
Geth left,
Geth joined
22:36
sugarbeet joined
|
|||
| timo | oh, and i'm glad to see brrt again :) | 23:03 | |
|
23:30
epony left
|
|||