diff options
author | Wilco Dijkstra <wilco.dijkstra@arm.com> | 2024-06-20 11:43:54 +0100 |
---|---|---|
committer | Wilco Dijkstra <wilco.dijkstra@arm.com> | 2024-06-21 14:41:42 +0100 |
commit | 5aa2f79691ca6a40a59dfd4a2d6f7baff6917eb7 (patch) | |
tree | 85517f5fd684fd00eca4e6f14735ea33f1bd6e64 /sysdeps/hppa/fpu | |
parent | da61ba3f8930e9b39fe35f88cb2ed4bc4571e598 (diff) | |
download | glibc-5aa2f79691ca6a40a59dfd4a2d6f7baff6917eb7.tar.gz glibc-5aa2f79691ca6a40a59dfd4a2d6f7baff6917eb7.tar.xz glibc-5aa2f79691ca6a40a59dfd4a2d6f7baff6917eb7.zip |
Benchtests: Remove broken walk benchmarks
The walk benchmarks don't measure anything useful - memory is not initialized properly so doing a single walk in 32MB just measures reading the 4KB zero page for reads and clear_page overhead for writes. The memset variants don't even manage to do a walk in the 32MB region due to using incorrect pointer increments... Neither is it clear why it is walking backwards since this won't confuse modern prefetchers. If you fix the benchmark and print the bandwidth, the results are identical for all sizes larger than ~1KB since it is just testing memory bandwidth of a single 32MB block. This case is already tested by the large benchmark, so overall it doesn't seem useful to keep these. Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Diffstat (limited to 'sysdeps/hppa/fpu')
0 files changed, 0 insertions, 0 deletions