From: Jakob Stoklund Olesen <stoklund@2pi.dk>
Date: Tue, 31 Aug 2010 22:01:07 +0000 (+0000)
Subject: Stack slot access methods are in TargetInstrInfo.
X-Git-Tag: llvmorg-2.8.0-rc0~359
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=94e90b94063768557ee0ac200c2235c5ff33c2bf;p=platform%2Fupstream%2Fllvm.git

Stack slot access methods are in TargetInstrInfo.

llvm-svn: 112653
---

diff --git a/llvm/docs/CodeGenerator.html b/llvm/docs/CodeGenerator.html
index 8b1db7ac3da7..4d0813fd6dc8 100644
--- a/llvm/docs/CodeGenerator.html
+++ b/llvm/docs/CodeGenerator.html
@@ -1457,8 +1457,8 @@ bool RegMapping_Fer::compatible_class(MachineFunction &amp;mf,
    order to get and store values in memory. To assign a physical register to a
    virtual register present in a given operand,
    use <tt>MachineOperand::setReg(p_reg)</tt>. To insert a store instruction,
-   use <tt>TargetRegisterInfo::storeRegToStackSlot(...)</tt>, and to insert a
-   load instruction, use <tt>TargetRegisterInfo::loadRegFromStackSlot</tt>.</p>
+   use <tt>TargetInstrInfo::storeRegToStackSlot(...)</tt>, and to insert a
+   load instruction, use <tt>TargetInstrInfo::loadRegFromStackSlot</tt>.</p>
 
 <p>The indirect mapping shields the application developer from the complexities
    of inserting load and store instructions. In order to map a virtual register