aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/AsmPrinter/CodeViewDebug.cpp
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@sifive.com>2022-03-11 15:29:26 -0800
committerCraig Topper <craig.topper@sifive.com>2022-03-11 18:02:38 -0800
commitfa62c5326a9d74a52ed0678db470a3d759f1602a (patch)
tree1b5cb4fce295ffc16310b946ff31b4a3505e7763 /llvm/lib/CodeGen/AsmPrinter/CodeViewDebug.cpp
parenta7b1dccf7a9d9d742567ad0bbac51c7f70308137 (diff)
downloadllvm-fa62c5326a9d74a52ed0678db470a3d759f1602a.zip
llvm-fa62c5326a9d74a52ed0678db470a3d759f1602a.tar.gz
llvm-fa62c5326a9d74a52ed0678db470a3d759f1602a.tar.bz2
[RISCV] Add test cases that show that we're too aggressive about using greviw/gorciw. NFC
We currently type legalize to the W form, but type legalization doesn't place any requirements on the extended bits. So we are ok to use GREVI/GORCI for type legalization as long as the control doesn't cross any bits from the extended bits into the lower bits. This can allow us to recognize cases where the extended bits end up being all zeros and we can propagate that information through. My plan is to move greviw/gorciw formation to isel patterns similar to slliw.
Diffstat (limited to 'llvm/lib/CodeGen/AsmPrinter/CodeViewDebug.cpp')
0 files changed, 0 insertions, 0 deletions