- Mar 31, 2011
-
-
Akira Hatanaka authored
llvm-svn: 128650
-
Nick Lewycky authored
isn't an exact float. Also "fpext float 1.0 to float" is invalid IR because it's not performing an extension. llvm-svn: 128647
-
Jakob Stoklund Olesen authored
Turn them into noop KILL instructions instead. This lets the scavenger know when super-registers are killed and defined. llvm-svn: 128645
-
Johnny Chen authored
A8.6.23 BLX (immediate) rdar://problem/9212921 llvm-svn: 128644
-
Jakob Stoklund Olesen authored
llvm-svn: 128643
-
Jakob Stoklund Olesen authored
This way, shrinkToUses() will ignore the instruction that is about to be deleted, and we avoid leaving invalid live ranges that SplitKit doesn't like. Fix a misunderstanding in MachineVerifier about <def,undef> operands. The <undef> flag is valid on def operands where it has the same meaning as <undef> on a use operand. It only applies to sub-register defines which also read the full register. llvm-svn: 128642
-
Daniel Dunbar authored
llvm-svn: 128640
-
Devang Patel authored
llvm-svn: 128639
-
Bruno Cardoso Lopes authored
llvm-svn: 128635
-
Jakob Stoklund Olesen authored
llvm-svn: 128634
-
Richard Osborne authored
llvm-svn: 128633
-
Bruno Cardoso Lopes authored
- Implement asm parsing support for LDRT, LDRBT, STRT, STRBT and {STR,LDC}{2}_{PRE,POST} fixing the encoding wherever is possible. - Move all instructions which use am2offset without a pattern to use addrmode2. - Add a new encoding bit to describe the index mode used and teach printAddrMode2Operand to check by the addressing mode which index mode to print. - Testcases llvm-svn: 128632
-
Michael J. Spencer authored
llvm-svn: 128631
-
Michael J. Spencer authored
llvm-svn: 128630
-
NAKAMURA Takumi authored
We don't expect the real "powf()" on some hosts (and powf() would be available on other hosts). For consistency, std::pow(double,double) may be called instead. Or, precision issue might attack us, to see unstable regalloc and stack coloring. llvm-svn: 128629
-
Benjamin Kramer authored
Thanks Frits! llvm-svn: 128628
-
Benjamin Kramer authored
llvm-svn: 128627
-
Benjamin Kramer authored
llvm-svn: 128626
-
Benjamin Kramer authored
InstCombine: Shrink "fcmp (fpext x), C" to "fcmp x, C" if C can be losslessly converted to the type of x. Fixes PR9592. llvm-svn: 128625
-
Benjamin Kramer authored
llvm-svn: 128624
-
Duncan Sands authored
llvm-svn: 128623
-
Duncan Sands authored
llvm-svn: 128622
-
Bill Wendling authored
llvm-svn: 128620
-
Jakob Stoklund Olesen authored
The rematerialized instruction may require a more constrained register class than the register being spilled. In the test case, the spilled register has been inflated to the DPR register class, but we are rematerializing a load of the ssub_0 sub-register which only exists for DPR_VFP2 registers. The register class is reinflated after spilling, so the conservative choice is only temporary. llvm-svn: 128610
-
Matt Beaumont-Gay authored
This revision introduced a dependency cycle, as nlewycky mentioned by email. llvm-svn: 128597
-
Nick Lewycky authored
llvm-svn: 128594
-
Bob Wilson authored
llvm-svn: 128591
-
Owen Anderson authored
Somehow we managed to forget to encode the lane index for a large swathe of NEON instructions. With this fix, the entire test-suite passes with the Thumb integrated assembler. llvm-svn: 128587
-
Evan Cheng authored
llvm-svn: 128586
-
Bruno Cardoso Lopes authored
{STR,LDC}{2}_PRE. - Fixed the encoding in some places. - Some of those instructions were using am2offset and now use addrmode2. Codegen isn't affected, instructions which use SelectAddrMode2Offset were not touched. - Teach printAddrMode2Operand to check by the addressing mode which index mode to print. - This is a work in progress, more work to come. The idea is to change places which use am2offset to use addrmode2 instead, as to unify assembly parser. - Add testcases for assembly parser llvm-svn: 128585
-
Cameron Zwarich authored
can be recognized. This fixes <rdar://problem/9183078>. llvm-svn: 128584
-
Jim Grosbach authored
llvm-svn: 128583
-
- Mar 30, 2011
-
-
Bill Wendling authored
that one of the numbers is signed while the other is unsigned. This could lead to a wrong result when the signed was promoted to an unsigned int. * Add the data layout line to the testcase so that it will test the appropriate thing. Patch by David Terei! llvm-svn: 128577
-
Akira Hatanaka authored
llvm-svn: 128574
-
Jakob Stoklund Olesen authored
Prevent infinite growth of the list. Patch by José Fonseca! llvm-svn: 128568
-
Jakob Stoklund Olesen authored
StringMap was not properly updating NumTombstones after a clear or rehash. This was not fatal until now because the table was growing faster than NumTombstones could, but with the previous change of preventing infinite growth of the table the invariant (NumItems + NumTombstones <= NumBuckets) stopped being observed, causing infinite loops in certain situations. Patch by José Fonseca! llvm-svn: 128567
-
Jakob Stoklund Olesen authored
Rehash but don't grow when full of tombstones. Patch by José Fonseca! llvm-svn: 128566
-
Jakob Stoklund Olesen authored
Rehash but don't grow when full of tombstones. Patch by José Fonseca! llvm-svn: 128565
-
Jakob Stoklund Olesen authored
When the hash function uses object pointers all free entries eventually become tombstones as they are used at least once, regardless of the size. DenseMap cannot function with zero empty keys, so it double size to get get ridof the tombstones. However DenseMap never shrinks automatically unless it is cleared, so the net result is that certain tables grow infinitely. The solution is to make a fresh copy of the table without tombstones instead of doubling size, by simply calling grow with the current size. Patch by José Fonseca! llvm-svn: 128564
-
Jakob Stoklund Olesen authored
The rewriter can keep track of multiple stack slots in the same register if they happen to have the same value. When an instruction modifies a stack slot by defining a register that is mapped to a stack slot, other stack slots in that register are no longer valid. This is a very rare problem, and I don't have a simple test case. I get the impression that VirtRegRewriter knows it is about to be deleted, inventing a last opaque problem. <rdar://problem/9204040> llvm-svn: 128562
-