|
github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm Set by AlexDaniel on 12 June 2018. |
|||
|
00:03
patrickz joined
00:07
patrickb left
00:49
Kaeipi joined,
Kaiepi left
01:12
Kaeipi left
01:13
Kaeipi joined
01:14
Kaeipi left
01:15
Kaeipi joined,
Kaeipi left
01:16
Kaeipi joined
01:17
Kaeipi left
01:19
Kaiepi joined
01:20
Kaiepi left
01:21
Kaiepi joined
01:22
Kaiepi left
01:23
Kaiepi joined,
Kaiepi left
01:27
Kaiepi joined
02:50
kawaii left
02:51
kawaii joined
03:20
Kaiepi left
03:21
Kaiepi joined
03:41
Kaiepi left,
Kaiepi joined
06:31
sena_kun joined
07:15
Kaeipi joined,
Kaiepi left
07:29
Kaeipi left
07:30
Kaeipi joined
07:37
Kaeipi left
07:38
Kaiepi joined
07:54
Kaiepi left,
Kaiepi joined
08:01
squashable6 left
08:03
Kaiepi left,
squashable6 joined
08:04
Kaiepi joined
08:08
Altai-man joined
08:10
sena_kun left
10:20
domidumont joined
10:25
domidumont left
10:28
domidumont joined
10:29
patrickz left
12:09
sena_kun joined
12:10
Altai-man left
|
|||
| Geth | MoarVM/eliminate-static-race-condition: 4905967917 | (Nicholas Clark)++ | 4 files Add `MVM_get_running_threads_context` to get the running thread's context Start with a fallback implementation using `uv_key_create`, `uv_key_set` and `uv_key_get`, to eliminate the static variable and make the code thread safe. Use this in `qsort`'s callback, which needs to call functions that take the ... (10 more lines) |
13:25 | |
| MoarVM/eliminate-static-race-condition: 73862d27d3 | (Nicholas Clark)++ | 2 files Add MVM_THREAD_LOCAL to declare variables with thread local storage If the compiler provides this, it's likely much faster than UV's API, which is (basically) POSIX thread local storage, and requires a function call for each "get". UV appears to rely on Win32 compilers supporting this. All recent gcc and clang versions support it, and seemingly also the vendor compilers on Solaris and AIX. ... (6 more lines) |
|||
| MoarVM: nwc10++ created pull request #1374: Eliminate static race condition |
13:26 | ||
| nwc10 | sigh, oops, missed a reword. Sadly it seems that the "much" in "likely much faster" isn't true when you're building shared library code. | 13:28 | |
| it *is* for regular code. | 13:29 | ||
| Geth | MoarVM/eliminate-static-race-condition: 8f5f92f9cf | (Nicholas Clark)++ | 2 files Add MVM_THREAD_LOCAL to declare variables with thread local storage If the compiler provides this, it's likely faster than UV's API, which is (basically) POSIX thread local storage, and requires a function call for each "get". UV appears to rely on Win32 compilers supporting this. All recent gcc and clang versions support it, and seemingly also the vendor compilers on Solaris and AIX. ... (6 more lines) |
14:07 | |
| MoarVM/eliminate-static-race-condition: 3786fe65b4 | (Nicholas Clark)++ | 3 files A probe for compiler thread local storage support. Not needed on Win32, as UV already exposes it there. |
|||
|
15:35
Kaiepi left
15:57
Kaiepi joined
16:01
Kaiepi left
16:08
Altai-man joined,
Kaiepi joined
16:10
sena_kun left
|
|||
| Geth | MoarVM: 004e4bc77a | (Nicholas Clark)++ | build/probe.pm The probe for `pthread_setname_np` needs prototypes from <string.h> The compiler warns about this (but still compiles it successfully). The default for probes is to discard all output, so this is hidden. |
17:32 | |
| MoarVM/eliminate-static-race-condition: 4cfde6edf1 | (Nicholas Clark)++ | 4 files Add `MVM_get_running_threads_context` to get the running thread's context Start with a fallback implementation using `uv_key_create`, `uv_key_set` and `uv_key_get`, to eliminate the static variable and make the code thread safe. Use this in `qsort`'s callback, which needs to call functions that take the ... (10 more lines) |
18:41 | ||
| MoarVM/eliminate-static-race-condition: ac941c0d59 | (Nicholas Clark)++ | 2 files Add MVM_THREAD_LOCAL to declare variables with thread local storage If the compiler provides this, it's likely faster than UV's API, which is (basically) POSIX thread local storage, and requires a function call for each "get". UV appears to rely on Win32 compilers supporting this. All recent gcc and clang versions support it, and seemingly also the vendor compilers on Solaris and AIX. ... (6 more lines) |
|||
| MoarVM/eliminate-static-race-condition: 8d68b18f99 | (Nicholas Clark)++ | 3 files A probe for compiler thread local storage support. Not needed on Win32, as UV already exposes it there. |
|||
|
18:55
domidumont left
|
|||
| Geth | MoarVM/void-prototypes: 1eda12a0a6 | (Nicholas Clark)++ | 5 files Use `foo(void)` instead of just `foo()` for functions that take no arguments Whilst the two are equivalent in C++, in C the latter is just a declaration not a prototype - it specifies the return type but not the parameters, meaning that the compiler can't actually check the parameters passed and report errors. An explicit `void` makes it a prototype, declaring that the function takes no arguments. ... (11 more lines) |
19:39 | |
| MoarVM: nwc10++ created pull request #1375: Use `foo(void)` instead of just `foo()` for functions that take no arguments |
19:40 | ||
|
20:09
sena_kun joined
20:10
Altai-man left
|
|||
| Geth | MoarVM: 1eda12a0a6 | (Nicholas Clark)++ | 5 files Use `foo(void)` instead of just `foo()` for functions that take no arguments Whilst the two are equivalent in C++, in C the latter is just a declaration not a prototype - it specifies the return type but not the parameters, meaning that the compiler can't actually check the parameters passed and report errors. An explicit `void` makes it a prototype, declaring that the function takes no arguments. ... (11 more lines) |
21:09 | |
|
22:11
sena_kun left
23:06
lizmat_ joined,
lizmat left,
lizmat_ is now known as lizmat
23:14
lizmat_ joined
23:15
lizmat__ joined
23:17
lizmat left,
lizmat__ is now known as lizmat
23:18
lizmat_ left
|
|||