forked from OSchip/llvm-project
21193f4b7e
Summary: Up until the point i have looked in the source, i didn't even understood that i can disable 'cluster' output. I have always silenced it via ` &> /dev/null`. (And hoped it wasn't contributing much of the run time.) While i expect that it has it's use-cases i never once needed it so far. If i forget to silence it, console is completely flooded with that output. How about not expecting users to opt-out of analyses, but to explicitly specify the analyses that should be performed? Reviewers: courbet, gchatelet Reviewed By: courbet Subscribers: tschuett, RKSimon, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D57648 llvm-svn: 353021 |
||
---|---|---|
.. | ||
analysis-inconsistencies-uops-backwards.test | ||
analysis-inconsistencies-uops.test | ||
analysis-uops-backwards.test | ||
analysis-uops-variant.test | ||
analysis-uops.test | ||
inverse_throughput-by-opcode-name.s | ||
latency-by-opcode-name.s | ||
lit.local.cfg | ||
uops-ADD32mi8.s | ||
uops-ADD32mr.s | ||
uops-ADD32rm.s | ||
uops-BEXTR32rm.s | ||
uops-BSF16rm.s | ||
uops-BTR64mr.s | ||
uops-VFMADDSS4rm.s | ||
uops-by-opcode-name.s |