[all-commits] [llvm/llvm-project] aca3f1: [libc][benchmark] allow benchmark to be built with...

[Schrodinger ZHU Yifan via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: aca3f14c0d24d6d3ddc376ebbe1b5b0636e12ed6
      https://github.com/llvm/llvm-project/commit/aca3f14c0d24d6d3ddc376ebbe1b5b0636e12ed6
  Author: Schrodinger ZHU Yifan <yfzhu at google.com>
  Date:   2026-06-25 (Thu, 25 Jun 2026)

  Changed paths:
    M libc/benchmarks/CMakeLists.txt
    M libc/benchmarks/JSON.cpp
    M libc/benchmarks/JSONTest.cpp
    M libc/benchmarks/LibcBenchmark.cpp
    M libc/benchmarks/LibcBenchmark.h
    M libc/benchmarks/LibcBenchmarkTest.cpp
    M libc/benchmarks/LibcFunctionPrototypes.h
    M libc/benchmarks/LibcMemoryBenchmark.cpp
    M libc/benchmarks/LibcMemoryBenchmark.h
    M libc/benchmarks/LibcMemoryBenchmarkMain.cpp
    M libc/benchmarks/LibcMemoryGoogleBenchmarkMain.cpp
    M libc/benchmarks/MemorySizeDistributions.cpp
    M libc/benchmarks/MemorySizeDistributions.h

  Log Message:
  -----------
  [libc][benchmark] allow benchmark to be built without llvm support (#200951)

Update benchmark to allow it to be built in runtimes driven mode. 

It is still useful to have an in-tree benchmark suite. On my side, I am
working on some allocators related benchmarks. Due to the broken state
of this in-tree benchmark suite, I have to frequently port changes
between two workspace. Also, having benchmark suite can make it easier
to track performance change in a consistent view.

Assisted-by: AI tools, checked manually



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications