aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp
diff options
context:
space:
mode:
authorRoman Lebedev <lebedev.ri@gmail.com>2020-09-25 00:30:54 +0300
committerRoman Lebedev <lebedev.ri@gmail.com>2020-09-25 00:36:42 +0300
commit9bcf7b1c7a139a455400df109d81c638b9e75150 (patch)
tree7be7d77a0e8fa64b7e0db77ccf20e17a371bbea5 /llvm/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp
parent31177949cb1d88d7dd32078d09a265b828d40826 (diff)
downloadllvm-9bcf7b1c7a139a455400df109d81c638b9e75150.zip
llvm-9bcf7b1c7a139a455400df109d81c638b9e75150.tar.gz
llvm-9bcf7b1c7a139a455400df109d81c638b9e75150.tar.bz2
[NFCI][IR] ConstantRangeTest: add basic scaffolding for next-gen precision/correctness testing
I have long complained that while we have exhaustive tests for ConstantRange, they are, uh, not good. The approach of groking our own constant range via exhaustive enumeration is, mysterious. It neither tells us without doubt that the result is conservatively correct, nor the precise match to the ConstantRange result tells us that the result is precise. But yeah, it's fast, i give it that. In short, there are three things that we need to check: 1. That ConstantRange result is conservatively correct 2. That ConstantRange range is reasonable 3. That ConstantRange result is reasonably precise So let's not just check the middle one, but all three. This provides precision test coverage for D88178.
Diffstat (limited to 'llvm/lib/CodeGen/AsmPrinter/DebugHandlerBase.cpp')
0 files changed, 0 insertions, 0 deletions