diff options
author | Craig Topper <craig.topper@sifive.com> | 2025-04-23 15:55:29 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-04-23 15:55:29 -0700 |
commit | 6388a7acf7e31fdc7b9c168bd6ce0f4d25c98cd0 (patch) | |
tree | ffca5ec2d53012f9cb7b25c7f36c126901d00e1c /lldb/source/Commands/CommandObjectProcess.cpp | |
parent | 0d00b6bc3b459122de47d16c5153887063f4ea4b (diff) | |
download | llvm-6388a7acf7e31fdc7b9c168bd6ce0f4d25c98cd0.zip llvm-6388a7acf7e31fdc7b9c168bd6ce0f4d25c98cd0.tar.gz llvm-6388a7acf7e31fdc7b9c168bd6ce0f4d25c98cd0.tar.bz2 |
[RISCV] Check the extension type for atomic loads in isel patterns. (#137019)
Previously we ignored the extension type and only used the memory type.
The extension type on RISC-V today can only be nonextload, extload, or
sextload. It is ok to treat extload as the same as sextload so ignoring
the extension type is fine.
For #136502, we want to support zextload as well so we will need to
disambiguate based on the extension type.
I wanted to use IsAtomic/IsZeroExtLoad/IsSignExtLoad/IsAnyExtLoad flags
from PatFrags to autogenerate the predicates, but those aren't hooked up
properly in tablegen for ISD::ATOMIC_LOAD. Fixing that will impact other
targets as almost all of them also ignore the extension type.
Diffstat (limited to 'lldb/source/Commands/CommandObjectProcess.cpp')
0 files changed, 0 insertions, 0 deletions