github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm Set by AlexDaniel on 12 June 2018. |
|||
00:00
lizmat left
01:06
Kaiepi joined,
Kaiepi left
01:09
Kaiepi joined
01:22
Kaypie joined,
Kaiepi left
03:41
lizmat joined
04:03
Kaypie left,
Kaypie joined
|
|||
samcv | MasterDuke: i have built it with flto and i didn't see many changes | 05:22 | |
05:30
domidumont joined
05:37
domidumont left,
domidumont joined
05:58
brrt joined
06:03
lizmat left
06:12
domidumont left
07:03
robertle joined
07:20
domidumont joined
08:00
lizmat joined
08:08
brrt left
|
|||
samcv | also working on implementing Fibonacci hashing | 08:16 | |
got around to fully looking at the article. and my favorite part is that it uses all the bits of the hash, so probably more secure | 08:17 | ||
09:40
zakharyas joined
10:32
statisfiable6 left,
releasable6 left,
notable6 left,
bloatable6 left,
nativecallable6 left,
unicodable6 left
10:42
committable6 joined,
reportable6 joined,
benchable6 joined,
greppable6 joined,
releasable6 joined,
bloatable6 joined,
unicodable6 joined
10:43
evalable6 joined,
notable6 joined,
nativecallable6 joined,
coverable6 joined,
statisfiable6 joined,
bisectable6 joined,
squashable6 joined,
quotable6 joined,
shareable6 joined,
undersightable6 joined
10:47
lizmat left
11:13
raschipi joined
|
|||
MasterDuke | samcv: Fibonacci hashing with/for the current uthash? or something new? | 11:17 | |
11:57
brrt joined
|
|||
brrt | \o | 11:58 | |
I advertised MoarVMs string handling for a bit: lemire.me/blog/2018/06/15/emojis-j...ent-308918 | 11:59 | ||
samcv++ | |||
(for looking into improving our hashing) | 12:00 | ||
re: concurrent lock-free hashmap, I can't seem to solve the problem of resizing, to my embarassement | 12:01 | ||
jnthn | brrt: I guess you've seen web.stanford.edu/class/ee380/Abstr...eeHash.pdf ? | 12:37 | |
13:26
lizmat joined
|
|||
brrt | i haven't | 13:46 | |
13:46
raschipi left
|
|||
brrt | that's interesting | 13:49 | |
jnthn | :) | 13:50 | |
Yeah, I have a collection of lock-free modules for some of the simpler cases (stack, queue, trie), and pondered doing the hash table one, but it's a comparatively big undertaking :) | 13:51 | ||
13:51
Kaypie left
|
|||
brrt | i was thinking of doing a linked hash table, it's kind of simpler to do that with CAS | 13:52 | |
the thing i can't figure out is how to do atomic resize | 13:54 | ||
14:00
zakharyas left
14:04
coverable6 left,
benchable6 left,
bisectable6 left,
evalable6 left,
unicodable6 left,
statisfiable6 left,
quotable6 left,
greppable6 left,
bloatable6 left,
notable6 left,
shareable6 left,
squashable6 left,
releasable6 left,
reportable6 left,
undersightable6 left,
committable6 left,
nativecallable6 left
|
|||
robertle | jnthn: you have a lock-free updateable trie? does that lie around somewhere by any chance? | 14:07 | |
timotimo | it's on the ecosystem | 14:08 | |
eco: Trie | |||
buggable | timotimo, Trie 'A Trie implementation': github.com/FCO/Trie 5 other matching results: modules.perl6.org/s/ | ||
timotimo | eco: Trie::Concurrent | ||
buggable | timotimo, Nothing found | ||
timotimo | eco: Concurrent::Trie | ||
buggable | timotimo, Concurrent::Trie 'A lock-free concurrent trie (Text Retrieval) data structure.': modules.perl6.org/dist/Concurrent::...cpan:JNTHN | ||
robertle | k, will have a look! | ||
14:33
dogbert17 joined
|
|||
samcv | MasterDuke: uthash | 14:35 | |
brrt | samcv: any explicit plans to replace it completely rather than fully? | 14:38 | |
no need to, btw, we basically forked dynasm as well | |||
*completely rather than partially :-) | |||
samcv | not atm | ||
timotimo | if linking moarvm takes such a long time with -flto, i wonder if gold can also do lto? | 14:42 | |
it's supposed to be very fast | |||
brrt | what's gold? | 14:47 | |
in this context i mean | |||
ilmari | another linker | 14:49 | |
MasterDuke | from google i think | ||
brrt | oh, i see | 14:50 | |
timotimo | yeah, since go always links everything statically, they have loads more symbols to put into their binaries, or something like that | 14:52 | |
iiuc gold does some multithreading at the very least | 14:53 | ||
brrt | i think gold predates go, if i read my wikipedia correctly | 14:55 | |
timotimo | oh, OK | ||
14:58
lizmat left
|
|||
samcv | yes gold predates go | 15:00 | |
ilmari | google are just really unimaginative when it comes to naming | 15:03 | |
MasterDuke | hm. i added -fuse-ld=gold as well as -flto=4, but took the same amount of time | 15:06 | |
however, i'm not even entirely sure i have gold installed... | 15:07 | ||
15:08
nativecallable6 joined,
greppable6 joined,
coverable6 joined,
committable6 joined,
bloatable6 joined,
notable6 joined,
quotable6 joined,
releasable6 joined,
evalable6 joined,
bisectable6 joined,
reportable6 joined
|
|||
timotimo | heh. | 15:08 | |
a good time to try out execsnoop perhaps? | |||
MasterDuke | don't know what that is | 15:09 | |
timotimo | it's a tool based on perf that tells you everything that gets exec'd by a process directly and indirectly | ||
i haven't actually tried it yet, but that's my idea of what it is | |||
it's another brendan gregg thing, like the flamegraphs thing and flamescope | 15:10 | ||
15:10
lizmat joined
|
|||
MasterDuke | cool | 15:10 | |
15:14
brrt left
|
|||
MasterDuke | well, changing /usr/bin/ld to be a symlink to /usr/bin/ld.gold didn't change the build time any | 15:18 | |
huh. /usr/bin/ld and /usr/bin/ld.gold have different sizes, but the output of -v for both of them is the same: GNU ld (GNU Binutils) 2.30 | 15:19 | ||
timotimo | i get GNU gold (version 2.29-13.fc27) 1.14 | 15:21 | |
MasterDuke | that was in arch linux. in kubuntu 18.04 i get 'GNU ld (GNU Binutils for Ubuntu) 2.30' and 'GNU gold (GNU Binutils for Ubuntu 2.30) 1.15' | 15:23 | |
15:24
domidumont left
15:59
brrt joined
16:07
zakharyas joined
16:19
zakharyas left
16:20
robertle left
16:36
domidumont joined
17:25
zakharyas joined
|
|||
Geth | MoarVM: 9d53069b04 | (Timo Paulssen)++ | src/jit/graph.c steal pow_i impl from interp.c for the jit |
17:31 | |
timotimo | wait, are we okay with new commits on master right now? | ||
brrt | ehm, i'm not against it, but i'm guessin we want extra-carefulness for rakudo star | 17:38 | |
timotimo | btw, surely there's a better implementation of pow_i out there than this? | ||
brrt | probably :-) | 17:41 | |
timotimo | and surely we know one of the two values often enough to generate better code at the jit stage :) | ||
brrt | also probably :-) | 17:44 | |
17:49
zakharyas left
17:57
zakharyas joined
|
|||
MasterDuke | star is next month isn't it? | 18:18 | |
timotimo: why the name pow_i_impl? there aren't any other *_impl functions | 18:20 | ||
timotimo | i didn't want to find a good place to put it %) | ||
MasterDuke | heh | 18:21 | |
18:30
lizmat left
18:33
shareable6 joined
18:39
zakharyas left
18:45
nativecallable6 left,
nativecallable6 joined
18:47
unicodable6 joined,
benchable6 joined,
squashable6 joined,
statisfiable6 joined,
undersightable6 joined
18:50
lizmat joined
19:24
domidumont left
|
|||
brrt | fwiw, 'where do i put this internal function' is one of the least of my worries :-) | 19:24 | |
19:52
brrt left
20:10
lizmat left
20:12
lizmat joined
20:27
lizmat left
20:32
lizmat joined
21:29
lizmat left
21:52
lizmat joined
23:19
[Coke] left,
[Coke] joined
23:23
lizmat left
|