aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Format/FormatTokenLexer.cpp
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@sifive.com>2025-05-23 13:40:27 -0700
committerGitHub <noreply@github.com>2025-05-23 13:40:27 -0700
commitcd60ee9d6ed807a650d87f246e8c5fa7aa67ce98 (patch)
treec452e821108eaff30915c1fab200832116381c77 /clang/lib/Format/FormatTokenLexer.cpp
parentdf03f7ed4cc9555c7f55945065a6e9c3c6ad5f11 (diff)
downloadllvm-cd60ee9d6ed807a650d87f246e8c5fa7aa67ce98.zip
llvm-cd60ee9d6ed807a650d87f246e8c5fa7aa67ce98.tar.gz
llvm-cd60ee9d6ed807a650d87f246e8c5fa7aa67ce98.tar.bz2
[RISCV] Prevent using dummy_reg_pair_with_x0 in more places. (#141273)
Similar to #141261. These aren't easy to test without write MIR tests in areas we don't currently have tests. I'm not sure we use X0_Pair anywhere today. I'm going to try to migrate RISCVMakeCompressible to use copyToReg so we can share that code instead of basically duplicating it. I'm still concerned that target independent code may fold an extract_subreg operation and get an incorrect register if we do start using X0_Pair. We may have to special case dummy_reg_pair_with_x0 in the encoder and printer to be safe.
Diffstat (limited to 'clang/lib/Format/FormatTokenLexer.cpp')
0 files changed, 0 insertions, 0 deletions