diff options
author | Roman Lebedev <lebedev.ri@gmail.com> | 2022-12-18 03:44:13 +0300 |
---|---|---|
committer | Roman Lebedev <lebedev.ri@gmail.com> | 2022-12-18 03:50:10 +0300 |
commit | a3400191137e7c991b89ebe72211790dae1648a1 (patch) | |
tree | f9b0f019aff91b9ef2cd362ea76d4309dbf75b8c /lldb/source/Commands/CommandObjectExpression.cpp | |
parent | d22f050e15cb8c941d488d9674329db320ef1783 (diff) | |
download | llvm-a3400191137e7c991b89ebe72211790dae1648a1.zip llvm-a3400191137e7c991b89ebe72211790dae1648a1.tar.gz llvm-a3400191137e7c991b89ebe72211790dae1648a1.tar.bz2 |
[llvm-exegesis] Unbreak `--benchmarks-file=<f>`
I'm absolutely flabbergasted by this.
I was absolutely sure this worked.
But apparently not.
When outputting to the file, we'd write a single `InstructionBenchmark`
to it, and then close the file. And for the next `InstructionBenchmark`,
we'd reopen the file, truncating it in process,
and thus the first `InstructionBenchmark` would be gone...
Diffstat (limited to 'lldb/source/Commands/CommandObjectExpression.cpp')
0 files changed, 0 insertions, 0 deletions