Takayuki Matsuoka

@Jay-Lokhande, thanks for your improvement. It seems good. Could you provide more complete result for further evaluation? I mean (1) We need the benchmark result of both of the original...

> To clarify: my benchmarks were run on a RISC-V environment using QEMU (software emulation), not physical hardware. Is it fine? It's fine for initial testing. But it may not...

> Why was this even consider reasonable? I'm not sure, but AFAIK this PR has tried to bring the same optimization from newer (gcc RISC-V) compilers to older ones. It...

@camel-cdr , Basically, our status of this issue is waiting for OP's investigation. If they come up with a better inline-asm solution for older compilers, that would be a great...

Hi @Ian-Clowes, thanks for your effort. But I have a quick question: how about bucktick "`" notation? (edit: bucktick noation is incompatible with `sh` and POSIX shells though) ```sh cd...

Hi @mi2think, We need further details of your issue/project. Could you provide how to reproduce your issue? ---- It seems you're using vcpkg. At least in my environment, I don't...

I don't know about a conclusion of this issue. But I think @himikof is raising some interesting demands which also require `LZ4_FREESTANDING`. - Demands - We're aware about decompression applications...

#894 is definitely an issue to be fixed. Since it minimizes future confusion. Anyway, here is a potential issues/PRs which may be referenced in the next release: https://github.com/Cyan4973/xxHash/issues?q=created%3A%3E%3D2023-07-21+

Hi @mofosyne , Our CI script has test for cmake + Visual Studio 2019/2022 with plain Windows VM. It may help you: https://github.com/Cyan4973/xxHash/blob/805c00b68fa754200ada0c207ffeaa7a4409377c/.github/workflows/ci.yml#L508-L578 Also, there're similar (but resolved) questions: -...

> ```C > #if defined(__STDC_VERSION__) && (__STDC_VERSION__ >= 201112L) \ > && (defined(_MSC_VER) && (_MSC_VER >= 1000) || !defined(_MSC_VER)) /* >= C11 */ > ``` It seems `_MSC_VER >= 1000`...