Jay Lokhande

Results 17 comments of Jay Lokhande

@Cyan4973 what do you think should we go ahead with proposed changes?

Hi, @t-mat Thank you for your suggestion. What do you think adding RISC-V support in xxHash will be beneficial would you like to give me any suggestions over it should...

> But this patch has some merit for older compilers. Therefore, I think we need benchmarks. It would be nice to have the result of `xxhsum`'s built-in benchmark. And we...

Hi @t-mat, Thanks again for the detailed suggestions and support throughout! I’ve set up multiple GCC versions (9 through 14) inside the RISC-V QEMU environment. [IMAGE](https://github.com/user-attachments/assets/879795a1-5a41-4015-9ebd-e61cd361edae) I’m using a benchmarking...

Hello @t-mat, ### 📊 xxHash Benchmark Results (Without Patch) [CLI-img](https://github.com/user-attachments/assets/2f0ef251-7201-4ef8-ba0a-6fa2e198c872) | GCC Version | 5#XXH3_64b (MB/s) | 11#XXH128 (MB/s) | 21#XXH3_stream (MB/s) | 25#XXH128_stream (MB/s) | |-------------|------------------|------------------|------------------------|--------------------------| | GCC-9 |...

Update on RISC-V implementation of XXH_mult32to64_add64: ```c #elif defined(__riscv) && (__riscv_xlen == 64) XXH_FORCE_INLINE xxh_u64 XXH_mult32to64_add64(xxh_u64 lhs, xxh_u64 rhs, xxh_u64 acc) { xxh_u64 ret; __asm__ ( "slli t0, %1, 32...

Hello @t-mat, ### 🛠️ xxHash Benchmark Results (With Patch) | GCC Version | 5#XXH3_64b (MB/s) | 11#XXH128 (MB/s) | 21#XXH3_stream (MB/s) | 25#XXH128_stream (MB/s) | |-------------|------------------|------------------|------------------------|--------------------------| | GCC-9 | 124.2...

@t-mat , Thank you for your feedback and detailed benchmarks. To clarify: my benchmarks were run on a RISC-V environment using QEMU (software emulation), not physical hardware. Is it fine?...

Hey, I would like to work on it