Jonathan Hallström

Results 25 comments of Jonathan Hallström

@memcpy: Don't check for aliasing if the type being copied has a bitSize of in 0

Seem CI is [still failing](https://github.com/ziglang/zig/actions/runs/11288829012/job/31397622151?pr=21658), maybe not emitting anything in the case of zero bit types will fix it?

@memcpy: Don't check for aliasing if the type being copied has a bitSize of in 0

This way of implementing it feels a little bit sketchy, maybe it should just be an early return?

@memcpy: Don't check for aliasing if the type being copied has a bitSize of in 0

i seem to have messed something up in git

std.mem.reverse: Improve performance

If you'd like I can send the benchmarks directly here, or you can see them at this link https://github.com/JonathanHallstrom/array_reversing/tree/main/bench_results. They are a little bit out of date but I will...

std.mem.reverse: Improve performance

You're quite right that constant size buffers get optimized, I'm relying on that in my implementation. It probably would have been good if I clarified that I meant I'm not...

std.mem.reverse: Improve performance

![bench_u8](https://github.com/ziglang/zig/assets/84847878/9353407b-2184-4b48-a314-da152d2bea16) ![bench_u64](https://github.com/ziglang/zig/assets/84847878/715a7121-cc58-4ced-8cad-a32e36257e67) Here are some of the benchmark results from my machine. `memset` is included to give a rough estimate of the memory bandwidth limit.

std.mem.reverse: Improve performance

Note that these benchmarks are not ideal as they're generated with the google benchmark library, and so the actual benchmarking code is not written in zig. Edit: This was done...

std.mem.reverse: Improve performance

~~Just noticed that my change seems [to make constant size array case worse](https://zig.godbolt.org/).~~ Accidentally used the wrong version of the code. Heres the up to date version, [no change for...

std.mem.reverse: Improve performance

I'm rerunning some of the benchmarks now so they'll be up to date.