[libc] Include CPU model in overlay CI sccache key (#196477)

[libc] Include CPU model in overlay CI sccache key

The overlay CI compiles opt_host memory tests with `-march=native`,
which generates object files specific to the runner CPU model. sccache
treats `-march=native` as a literal string in its hash key, so cached
`.o` files compiled on one CPU model get served to runners with a
different CPU. When the cached binary uses instructions the current CPU
lacks, the test crashes with SIGILL.

## Symptoms

The `memcmp_opt_host`, `memmove_opt_host`, `memset_opt_host`,
`bcmp_opt_host`, and `bzero_opt_host` tests crash when SIMD code paths
are first exercised. Simple tests like `CmpZeroByte` pass because they
use small sizes that do not enter SIMD routines. The failures are fully
reproducible on reruns because the cache stays poisoned.

## Evidence

Three consecutive runs of the same fwide PR (#196157), same code:

| Run | Azure Region | Cache Hits | Cache Misses | Result |
|-----|-------------|-----------|-------------|--------|
|
[25512875679](https://github.com/llvm/llvm-project/actions/runs/25512875679/job/74876008545)
| westus3 | 9 | 5354 | PASS |
|
[25524024922](https://github.com/llvm/llvm-project/actions/runs/25524024922/job/74916241365)
| northcentralus | 5345 | 0 | CRASH |
|
[25524839613](https://github.com/llvm/llvm-project/actions/runs/25524839613/job/74965830435)
| westus | 5345 | 0 | CRASH |

The first run had a nearly empty cache and compiled everything locally
(0.17% hit rate). An intermediate [syscall-unistd
run](https://github.com/llvm/llvm-project/actions/runs/25517783708/job/74893495220)
in eastus then populated the cache with object files compiled for that
region's CPU. Subsequent runs on different hardware got 100% cache hits
and crashed because the cached `.o` files use instructions their CPUs
lack.

## Fix

Added a "Detect CPU model" step that reads the CPU model string from
`/proc/cpuinfo` (Linux) or `sysctl` (macOS) and appends it to the
sccache cache key. Runners with different CPUs now get separate cache
buckets.

Assisted-by: Automated tooling, human reviewed.
1 file changed
tree: 9c6f21c1d3fe37a2e0b14d1bb576b2c3ea1df345
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

Welcome to the LLVM project!

This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.

C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.

Other components include: the libc++ C++ standard library, the LLD linker, and more.

Getting the Source Code and Building LLVM

Consult the Getting Started with LLVM page for information on building and running LLVM.

For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting in touch

Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.