- Jan 14, 2011
-
-
Jakob Stoklund Olesen authored
This approach also works when the terminator doesn't have a slot index. (Which can happen??) llvm-svn: 123413
-
- Jan 13, 2011
-
-
Jakob Stoklund Olesen authored
llvm-svn: 123400
-
Jakob Stoklund Olesen authored
llvm-svn: 123399
-
Devang Patel authored
llvm-svn: 123389
-
Jakob Stoklund Olesen authored
It will still return an iterator that points to the first terminator or end(), but there may be DBG_VALUE instructions following the first terminator. llvm-svn: 123384
-
Dan Gohman authored
llvm-svn: 123352
-
Jakob Stoklund Olesen authored
llvm-svn: 123351
-
Dan Gohman authored
further on the associated testcase before aborting. llvm-svn: 123346
-
Jakob Stoklund Olesen authored
llvm-svn: 123342
-
Jakob Stoklund Olesen authored
llvm-svn: 123339
-
Jakob Stoklund Olesen authored
llvm-svn: 123338
-
- Jan 12, 2011
-
-
Jakob Stoklund Olesen authored
Make sure we don't crash in that case, but simply turn them into %noreg instead. llvm-svn: 123335
-
Jakob Stoklund Olesen authored
It was leaving dangling pointers in the slot index maps. llvm-svn: 123334
-
Jakob Stoklund Olesen authored
llvm-svn: 123333
-
Jakob Stoklund Olesen authored
The slot indexes must be monotonically increasing through the function. llvm-svn: 123324
-
Jakob Stoklund Olesen authored
llvm-svn: 123322
-
Jakob Stoklund Olesen authored
llvm-svn: 123290
-
- Jan 11, 2011
-
-
Jakob Stoklund Olesen authored
llvm-svn: 123282
-
Jakob Stoklund Olesen authored
For one, MachineBasicBlock::getFirstTerminator() doesn't understand what is happening, and it also makes sense to have all control flow run through the DBG_VALUE. llvm-svn: 123277
-
Devang Patel authored
This is not yet completely enabled. llvm-svn: 123274
-
Eric Christopher authored
llvm-svn: 123202
-
- Jan 10, 2011
-
-
Dale Johannesen authored
There's an inherent tension in DAGCombine between assuming that things will be put in canonical form, and the Depth mechanism that disables transformations when recursion gets too deep. It would not surprise me if there's a lot of little bugs like this one waiting to be discovered. The mechanism seems fragile and I'd suggest looking at it from a design viewpoint. llvm-svn: 123191
-
Anton Korobeynikov authored
Rename TargetFrameInfo into TargetFrameLowering. Also, put couple of FIXMEs and fixes here and there. llvm-svn: 123170
-
Chris Lattner authored
rolled std::find. llvm-svn: 123164
-
Jakob Stoklund Olesen authored
These functions not longer assert when passed 0, but simply return false instead. No functional change intended. llvm-svn: 123155
-
- Jan 09, 2011
-
-
Jakob Stoklund Olesen authored
when no virtual registers have been allocated. It was only used to resize IndexedMaps, so provide an IndexedMap::resize() method such that Map.grow(MRI.getLastVirtReg()); can be replaced with the simpler Map.resize(MRI.getNumVirtRegs()); This works correctly when no virtuals are allocated, and it bypasses the to/from index conversions. llvm-svn: 123130
-
Chris Lattner authored
llvm-svn: 123129
-
Jakob Stoklund Olesen authored
physical register numbers. This makes the hack used in LiveInterval official, and lets LiveInterval be oblivious of stack slots. The isPhysicalRegister() and isVirtualRegister() predicates don't know about this, so when a variable may contain a stack slot, isStackSlot() should always be tested first. llvm-svn: 123128
-
Jakob Stoklund Olesen authored
llvm-svn: 123123
-
Cameron Zwarich authored
llvm-svn: 123115
-
Cameron Zwarich authored
llvm-svn: 123114
-
Jakob Stoklund Olesen authored
of using a Location class with the same information. When making a copy of a MachineOperand that was already stored in a MachineInstr, it is necessary to clear the parent pointer on the copy. Otherwise the register use-def lists become inconsistent. Add MachineOperand::clearParent() to do that. An alternative would be a custom MachineOperand copy constructor that cleared ParentMI. I didn't want to do that because of the performance impact. llvm-svn: 123109
-
Jakob Stoklund Olesen authored
llvm-svn: 123108
-
Jakob Stoklund Olesen authored
Print virtual registers numbered from 0 instead of the arbitrary FirstVirtualRegister. The first virtual register is printed as %vreg0. TRI::NoRegister is printed as %noreg. llvm-svn: 123107
-
Jakob Stoklund Olesen authored
llvm-svn: 123106
-
Jakob Stoklund Olesen authored
depending on TRI::FirstVirtualRegister. Also use TRI::printReg instead of printing virtual registers directly. llvm-svn: 123101
-
Jakob Stoklund Olesen authored
virtual registers. llvm-svn: 123100
-
Jakob Stoklund Olesen authored
Provide MRI::getNumVirtRegs() and TRI::index2VirtReg() functions to allow iteration over virtual registers without depending on the representation of virtual register numbers. llvm-svn: 123098
-
Jakob Stoklund Olesen authored
Use an IndexedMap for LiveOutRegInfo to hide its dependence on TargetRegisterInfo::FirstVirtualRegister. llvm-svn: 123096
-
- Jan 08, 2011
-
-
Cameron Zwarich authored
llvm-svn: 123093
-