summaryrefslogtreecommitdiff
path: root/libc/benchmarks/LibcMemoryBenchmark.cpp
AgeCommit message (Collapse)Author
2025-09-24[libc][NFC] Remove usage of the C keyword `I`. (#160567)lntue
2022-11-16[libc][benchmark] Fix wrong BatchSize leading to data not fitting in L1.Guillaume Chatelet
Differential Revision: https://reviews.llvm.org/D138111
2021-11-30[libc] Add memmove benchmarksGuillaume Chatelet
This patch enables the benchmarking of `memmove`. Ideally, this should be submitted before D114637. Differential Revision: https://reviews.llvm.org/D114694
2021-08-03[libc] Allow benchmarking several implementations at the same time.Guillaume Chatelet
Next step is to generate an archive with all implementations and a header listing them all. Differential Revision: https://reviews.llvm.org/D107336
2021-08-02[libc] Add a Google Benchmark target to support continuous monitoring of ↵Guillaume Chatelet
memory operation performance The next step is to be able to benchmark several implementations at once and compare which one performs best on a particular machine. Differential Revision: https://reviews.llvm.org/D107265
2021-07-28[libc] Simplify implementation of benchmarksGuillaume Chatelet
This also allows to run the distribution benchmarks in other frameworks like the Google Benchmark facility.
2020-12-17[libc] revamp memory function benchmarkGuillaume Chatelet
The benchmarking infrastructure can now run in two modes: - Sweep Mode: which generates a ramp of size values (same as before), - Distribution Mode: allows the user to select a distribution for the size paramater that is representative from production. The analysis tool has also been updated to handle both modes. Differential Revision: https://reviews.llvm.org/D93210
2020-06-17[libc][benchmarks] Link the memory benchmark exes to functions from LLVM libc.Siva Chandra Reddy
Summary: To get the target order correct, the benchmarks directory has been moved one level higher. Previously, it was living in the utils directory. The utils directory is a collection of utils which are to be used by the tests and implementations. However, benchmarks *use* the implementations. So, moving it out of utils helps us setup proper target level dependencies. Reviewers: gchatelet Differential Revision: https://reviews.llvm.org/D81910