The optimization level used when building the benchmarks should
match the optimization level of the current build. Otherwise, we
can end up mixing an -O3 or -O0 optimized dylib with benchmarks
built with -O2, which is really misleading.
Details
Details
- Reviewers
var-const Mordante - Group Reviewers
Restricted Project - Commits
- rG303c4c37ea49: [libc++] Don't force -O2 when building the benchmarks
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo