aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectFrame.cpp
diff options
context:
space:
mode:
authorBill Schmidt <wschmidt@linux.vnet.ibm.com>2013-02-21 00:38:25 +0000
committerBill Schmidt <wschmidt@linux.vnet.ibm.com>2013-02-21 00:38:25 +0000
commitf5b474c6c6c05689fb1a0dae7c24dec161d87917 (patch)
treeec8bceafe429b47c9186cde37c865f500ccbe3c8 /lldb/source/Commands/CommandObjectFrame.cpp
parentef04593de1bf4cc370131dd54f89b11637c53024 (diff)
downloadllvm-f5b474c6c6c05689fb1a0dae7c24dec161d87917.zip
llvm-f5b474c6c6c05689fb1a0dae7c24dec161d87917.tar.gz
llvm-f5b474c6c6c05689fb1a0dae7c24dec161d87917.tar.bz2
PPCDAGToDAGISel::PostprocessISelDAG()
This patch implements the PPCDAGToDAGISel::PostprocessISelDAG virtual method to perform post-selection peephole optimizations on the DAG representation. One optimization is implemented here: folds to clean up complex addressing expressions for thread-local storage and medium code model. It will also be useful for large code model sequences when those are added later. I originally thought about doing this on the MI representation prior to register assignment, but it's difficult to do effective global dead code elimination at that point. DCE is trivial on the DAG representation. A typical example of a candidate code sequence in assembly: addis 3, 2, globalvar@toc@ha addi 3, 3, globalvar@toc@l lwz 5, 0(3) When the final instruction is a load or store with an immediate offset of zero, the offset from the add-immediate can replace the zero, provided the relocation information is carried along: addis 3, 2, globalvar@toc@ha lwz 5, globalvar@toc@l(3) Since the addi can in general have multiple uses, we need to only delete the instruction when the last use is removed. llvm-svn: 175697
Diffstat (limited to 'lldb/source/Commands/CommandObjectFrame.cpp')
0 files changed, 0 insertions, 0 deletions