| lizmat | [Coke]: I don't think it is anymore, but am not 100% sure | 00:09 | |
| afk& | |||
| Geth | MoarVM: coke self-assigned 2025.01 tarball from releases is broken and does not extract: `gnutar: Archive value is out of time_t range` github.com/MoarVM/MoarVM/issues/1905 frou++ created pull request #1909: Fix error message typo in build probe script |
02:16 | |
|
08:45
sena_kun joined
|
|||
| lizmat | and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2025/02/03/2025-...ie-awaits/ | 12:31 | |
|
13:32
japhb left
|
|||
| MoarVM/main: ce521cf9a7 | (Duncan Holm)++ (committed using GitHub Web editor) | build/probe.pm Fix error message typo in build probe script |
14:58 | ||
|
16:43
japhb joined
|
|||
| timo | MasterDuke, do you know if that "check for numbers above 127" loop can be broken out of while still being vectorized? also, do you happen to have stats of what lengths of string happen how often? | 20:09 | |
| do you know what the target architecture is that your gcc is compiling for? i.e. if any particular -march= is active? can you try CFLAGS=-march=native and see if that makes a difference? that will target your exact processor with all its capabilities, rather than something that uses only stuff that can be assumed to be there ... not actually sure what the exact decisionmaking is based on? | 20:13 | ||
|
23:51
sena_kun left
|
|||