cpuinfo icon indicating copy to clipboard operation
cpuinfo copied to clipboard

CPU INFOrmation library (x86/x86-64/ARM/ARM64, Linux/Windows/Android/macOS/iOS)

Results 105 cpuinfo issues
Sort by recently updated
recently updated
newest added

**Platform**:android_arm64-android13 **SOC**: cortex A 4*a55 and 4*a76 **Cpuinfo**:core_siblings_list:0-7 **HW**:design 4*a55 and 4*a76 as a cluster on SOC and configure dtsi cpu 8core as a cluster. **Problem**:Use benchmark tools test CPU...

bug

``` SoC name: Unknown Microarchitectures: 4x Cortex-A77 4x Cortex-A55 Cores: 0: 1 processor (0), ARM Cortex-A77 1: 1 processor (1), ARM Cortex-A77 2: 1 processor (2), ARM Cortex-A77 3: 1...

enhancement

hwcap and hwcap2 are 64bit values on arm64 linux so consistently using uint32_t for it is wrong. (top 32bit of hwcap is reserved for libc use so may not be...

bug

CMAKE_SYSTEM_PROCESSOR is not set by cmake on apple platforms which causes this warning: ``` MESSAGE(WARNING "Target processor architecture is not specified. " "cpuinfo will compile, but cpuinfo_initialize() will always fail.")...

bug

Similar to our other Android targets in the workflows, we should add an Android RISC-V build target. This isn't currently trivial, because the Android NDK w/RISC-V support is only in...

enhancement

The name of the SOC is not displaying

enhancement

I have my own builds of the **GTest** and **benchmark** libraries that I want to use in the cpuinfo build, but the `USE_SYSTEM_LIBS` option assumes that these are installed in...

cla signed

Users of the library can choose to release all resources the library may have allocated as part of a previous cpuinfo_initialize call. If no resources were previously allocated, this function...

cla signed

We should ideally have at least one RISC-V board in our test group to limit future regression. Further work will have to be done to actually enable a toolchain that...

cla signed