Add testcases to llvm test/ to make sure that the combined middle-end
optimizations do not regress on optimizing the number of loads in the loops.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I thought we frown on multi-pass regression tests, let alone -O2.
Based on the comments in PR30188 ( https://llvm.org/bugs/show_bug.cgi?id=30188 ) - if the goal is to make sure that BinarySearch perf does not regress, is a better solution to add that C source app to test-suite's Benchmarks dir, so we can make sure that the end-to-end perf is what we want?