yzazik

@ganeshmarkandan I'm cross-compiling google/benchmark for armv8a/neon (from either Windows or Linux) with Android NDK-26, runs with no issues, but I'm using clang-llvm (better SIMD code gen). I do have GCC4.9...

@kfjahnke > I think SIMD-affine people tend to make a mistake: they want to harness the SIMD capabilities of a given hardware. Then they look for a way to code...

@hayguen I guess, you would use LUT to convert each byte/nibble to a number of set bits in it, then shuffle/permute and sum till you reach your lane width. Some...

Second on this, can't cross-compile for Windows ARM64 on x64 host with 1.2.0, not even with head. But can compile it on the ARM64 host with head, but not with...

I'm having troubles with this on Windows, cl (VS2022) throws: C:\github\printf\src\printf\printf.c(956): warning C4701: potentially uninitialized local variable 'abs_exp10_covered_by_powers_table' used Out of curiosity, how much troubles would it cause to simply...

Ok, let me start over, I just need to understand the intent and explain this more. Not the test code [per se], but [rather] an example code (skeleton_test is in...

Oh no, dynamic library support should not be dropped. Half of the world won't be happy, myself including. Most of the things in our project born to be dynamic. Often...

True, **putchar_**() is essential to **printf**() but, as I said, I'm not interested in **printf**(). I'm only using **fctprintf**() and it does not need **putchar_**(), it needs void (****out**)(char c,...

Well, I could, but we have a Windows customer and for Windows build this doesn't work with none of GCC (mingw64), LLVM, Cl (with /opt:ref) or ClangCL.

Different translation unit (ie extra .c file) would work just fine too. I'd guess, static functions are only static there to avoid name collisions. You could just use longer and...