| 15 May 2024 | |||
| lizmat | actually: src/io/syncfile.c:486:1: error: version control conflict marker in file | 15:55 | |
| ab5tract | ahh, some cherry-pick merge gunk | 15:56 | |
| sorry about that :( | |||
| lizmat | CI for the win! | ||
| ab5tract | love that stuff | 16:00 | |
| should be un-borked now | |||
| nine | lizmat: do you mean in the bytecode files? | 17:07 | |
| lizmat | possibly? but yeah, you're right, I shouldn't equate bytecode format with in-memory layout, right? | 17:10 | |
| otoh, why do we align on 2/4 byte boundaries in the bytecode format? to allow for easier reading, right ? | 17:11 | ||
| 18 May 2024 | |||
| Geth | MoarVM: MasterDuke17++ created pull request #1805: Cleanup variables in bigint ops error cases |
03:15 | |
| MoarVM/main: dbdfb3999b | MasterDuke17++ (committed using GitHub Web editor) | src/math/bigintops.c Cleanup variables in bigint ops error cases In a bunch of error cases of bigint ops we weren't always cleaning up all the variables. These were noticed when investigating github.com/MoarVM/MoarVM/issues/1804, but I don't think they are the actual cause. |
08:55 | ||
| MoarVM/main: c9dd4dd964 | (Daniel Green)++ | src/jit/x64/emit.dasc Silence incorrect GCC warning The three branches of the `if/else if` correspond to the three `case`s that can enter this block, so the variable will always be initialized when used. |
14:13 | ||
| MasterDuke | huh. not sure why we have the free_at_safepoint mutex github.com/MoarVM/MoarVM/blob/main...ce.h#L225. it's only ever used once github.com/MoarVM/MoarVM/blob/main....c#L80-L87 when setting the debug name on a type | 20:03 | |
| tellable6 | 2024-05-18T12:48:25Z #raku-dev <ab5tract> MasterDuke17: thanks for the review on the MoarVM PR. Somehow I didn't get pinged about them in the GH app | ||
| 19 May 2024 | |||
| Geth | MoarVM: MasterDuke17++ created pull request #1806: Switch free_at_safepoint linked list (back) to a vector |
01:27 | |
| MoarVM: ab5tract++ created pull request #1807: Update 2021.10 -> 2024.05 |
11:19 | ||
| ab5tract | ^^ this is just to check the CI pipelines against a no-op PR | 11:20 | |
| Geth | MoarVM: MasterDuke17++ created pull request #1808: Add missing __builtin_clz definition for MSVC |
17:58 | |
| MoarVM: MasterDuke17++ created pull request #1809: Cheat to speedup using nqp::iterator+nqp::shift on a list |
18:21 | ||
| jdv | yeah, maybe don't change something unless you're sure. | 18:46 | |
| that longer version # is somewhere else in the file | |||
| or maybe not, huh. anyway, i think its because of tag and branch naming conflicts in that guide. | 18:48 | ||
| 20 May 2024 | |||
| Geth | MoarVM/main: fe2080ac38 | ab5tract++ (committed using GitHub Web editor) | 3 files Provide some mechanisms for introspecting file mode In order to avoid adding yet-another member variable to IO::Handle, we instead provide some new syscalls for inquiring about the mode of the underlying BOOTIO object. ... (10 more lines) |
15:22 | |
| lizmat | And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2024/05/20/2024-...ry-primed/ | 16:36 | |
| 21 May 2024 | |||
| [Coke] | regarding R#5574 - looks like pod::to::text just doesn't care about Z<>, might have a quick fix. | 19:55 | |
| linkable6 | R#5574 [open]: github.com/rakudo/rakudo/issues/5574 Z<> not working | ||