aboutsummaryrefslogtreecommitdiff
path: root/clang-tools-extra/clang-doc/BitcodeReader.cpp
diff options
context:
space:
mode:
authorAmy Kwan <amy.kwan1@ibm.com>2022-12-06 11:52:52 -0600
committerAmy Kwan <amy.kwan1@ibm.com>2022-12-06 14:23:50 -0600
commit48634b3b935fd0bb325c08fce6313fadcdcb6f86 (patch)
treecfdce97445e506b8018a7f8a9efa0f18aeeeb42e /clang-tools-extra/clang-doc/BitcodeReader.cpp
parent5ad919a1d6bbe449210f81e4ae7a5f765eb5a976 (diff)
downloadllvm-48634b3b935fd0bb325c08fce6313fadcdcb6f86.zip
llvm-48634b3b935fd0bb325c08fce6313fadcdcb6f86.tar.gz
llvm-48634b3b935fd0bb325c08fce6313fadcdcb6f86.tar.bz2
[NFC][PowerPC] Add NFC fixes to PPCInstrinfo.cpp when getting the defined machine instruction.
This patch adds the following NFC fixes to PPCInstrInfo.cpp when getting the DefMI: - Fix documentation error to state that we want to flag a use of register between the def and the MI (in post-RA) - Setting the DefMI to null if the DefMI is neither an LI or and ADDI (while still being in SSA form). In terms of setting the DefMI to null, this change aims to account for the scenario of when we end up going through all operands on the machine instruction MI and updating OpNoForForwarding accordingly once an ADDI is found as the DefMI. It is possible that once an ADDI is found, we will continue to go through all operands in attempts to find an LI, but end up looking at every operand until we reach the end if we have not yet found an LI. In the case where the end is reached and we never end up finding an LI/ADDI, DefMI would be pointing to the last operand of MI while OpNoForForwarding would still be pointing at the previous ADDI operand found. We reset DefMI to avoid having DefMI point to an instruction that differs from the one represented by OpNoForForwarding. Differential Revision: https://reviews.llvm.org/D137483
Diffstat (limited to 'clang-tools-extra/clang-doc/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions