Maratyszcza
Maratyszcza
How do you differentiate M1/M1 Pro/M2/etc?
The current solution would likely produce wrong results on M2, which is a big no for cpuinfo. I'd rather have it report `unknown` that report wrong data. Please borrow an...
Without the ability to distinguish variants of Apple Silicon all we can do is set `vendor` to `cpuinfo_vendor_apple`, as all other information is unreliable. Narrowing down this change to just...
One hint might be the CP4020...CP5801 values reported in the registry. They are evidently different across M1 and M2, but it is unclear what they represent. CP4020 looks like MIDR,...
[This source snippet](https://github.com/ziglang/zig/blob/0461a64a93f0596e98b62d596bb547e5455577d2/lib/std/zig/system/windows.zig#L243-L255) suggest that CP NNN these are indeed system registers.
Which Android NDK version do you use?
This looks like a Clang bug. Note that it only happens when building source files for ARMv6. It looks like Clang assembly validator assumes that VFP registers are not supported...
XNNPack passes `-march=armv6 -mfpu=vfp` for the file that fails to compile. So it is building for ARMv6 with VFPv2.
ARMv7 build for XNNPack really means 32-bit ARM architecture. The minimal requirements for 32-bit ARM architecture in XNNPack is ARMv6 with VFPv2. Thus, XNNPack includes ARMv6+VFPv2-optimized microkernels in ARMv7 build,...
Fixed in #129