aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorAlex Bradbury <asb@igalia.com>2023-11-16 14:43:31 +0000
committerGitHub <noreply@github.com>2023-11-16 14:43:31 +0000
commit7f28e8ced7ef36a51e5cbca08818288ab167a8ab (patch)
tree90efac439b2de7cd67c9e4f0eea72f334636fe90 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parent181b2c1b4aae09b9d3bdd0c4f8fda705cccf1b5b (diff)
downloadllvm-7f28e8ced7ef36a51e5cbca08818288ab167a8ab.zip
llvm-7f28e8ced7ef36a51e5cbca08818288ab167a8ab.tar.gz
llvm-7f28e8ced7ef36a51e5cbca08818288ab167a8ab.tar.bz2
[RISCV] Implement RISCVInstrInfo::isAddImmediate (#72356)
This hook is called by the target-independent implementation of TargetInstrInfo::describeLoadedValue. I've opted to test it via a C++ unit test, which although fiddly to set up seems the right way to test a function with such clear intended semantics (rather than testing the impact indirectly). isAddImmediate will never recognise ADDIW as an add immediate which I _think_ is conservatively correct, as the caller may not understand its semantics vs ADDI. Note that although the doc comment for isAddImmediate specifies its behaviour solely in terms of physical registers, none of the current in-tree implementations (including this one) bail out on virtual registers (see #72357).
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions