- Jun 08, 2010
-
-
Bob Wilson authored
that it is an immediate before checking that the instruction is an EXTRACT_SUBREG. llvm-svn: 105585
-
Dan Gohman authored
llvm-svn: 105561
-
- Jun 07, 2010
-
-
Jim Grosbach authored
rdar://7797940 llvm-svn: 105557
-
Jim Grosbach authored
llvm-svn: 105554
-
Dan Gohman authored
llvm-svn: 105551
-
Dan Gohman authored
determinstic. Instead, give SCEV objects an arbitrary sequence number. llvm-svn: 105548
-
Dan Gohman authored
that the operands are sorted. llvm-svn: 105546
-
Bill Wendling authored
the operands. llvm-svn: 105545
-
Dan Gohman authored
llvm-svn: 105544
-
Dan Gohman authored
llvm-svn: 105542
-
Jim Grosbach authored
llvm-svn: 105541
-
Dan Gohman authored
scrounging through SCEVUnknown contents and SCEVNAryExpr operands; instead just do a simple deterministic comparison of the precomputed hash data. Also, since this is more precise, it eliminates the need for the slow N^2 duplicate detection code. llvm-svn: 105540
-
Bill Wendling authored
encapsulation to force the users of these classes to know about the internal data structure of the Operands structure. It also can lead to errors, like in the MSIL writer. llvm-svn: 105539
-
- Jun 05, 2010
-
-
Kenneth Uildriks authored
Partial specialization was not checking the callsite to make sure it was using the same constants as the specialization, leading to calls to the wrong specialization. Patch by Takumi Nakamura\! llvm-svn: 105528
-
Duncan Sands authored
llvm-svn: 105527
-
Chris Lattner authored
In file included from X86InstrInfo.cpp:16: X86GenInstrInfo.inc:2789: error: integer constant is too large for 'long' type X86GenInstrInfo.inc:2790: error: integer constant is too large for 'long' type X86GenInstrInfo.inc:2792: error: integer constant is too large for 'long' type X86GenInstrInfo.inc:2793: error: integer constant is too large for 'long' type X86GenInstrInfo.inc:2808: error: integer constant is too large for 'long' type X86GenInstrInfo.inc:2809: error: integer constant is too large for 'long' type X86GenInstrInfo.inc:2816: error: integer constant is too large for 'long' type X86GenInstrInfo.inc:2817: error: integer constant is too large for 'long' type llvm-svn: 105524
-
Bruno Cardoso Lopes authored
yet, only assembly encoding support. llvm-svn: 105521
-
Dale Johannesen authored
unless using -arm-tail-calls. llvm-svn: 105515
-
Dan Gohman authored
llvm-svn: 105514
-
Stuart Hastings authored
llvm-svn: 105511
-
Dan Gohman authored
there could be multiple subexpressions within a single expansion which require insert point adjustment. This fixes PR7306. llvm-svn: 105510
-
Dale Johannesen authored
I don't think this ever resulted in problems on x86, but it would on ARM. llvm-svn: 105509
-
Evan Cheng authored
llvm-svn: 105502
-
Dan Gohman authored
register pressure. llvm-svn: 105501
-
-
Stuart Hastings authored
llvm-svn: 105492
-
Devang Patel authored
Copy location info for current function argument from dbg.declare if respective store instruction does not have any location info. llvm-svn: 105490
-
- Jun 04, 2010
-
-
Jim Grosbach authored
llvm-svn: 105481
-
Dan Gohman authored
llvm-svn: 105480
-
Jakob Stoklund Olesen authored
register allocation. Process all of the clobber lists at the end of the function, marking the registers as used in MachineRegisterInfo. This is necessary in case the calls clobber callee-saved registers (sic). llvm-svn: 105473
-
Dale Johannesen authored
8060143, although this doesn't fix the real problem with tail call. llvm-svn: 105472
-
-
Jim Grosbach authored
llvm-svn: 105454
-
Mon P Wang authored
replace an OpA with a widened OpB, it is possible to get new uses of OpA due to CSE when recursively updating nodes. Since OpA has been processed, the new uses are not examined again. The patch checks if this occurred and it it did, updates the new uses of OpA to use OpB. llvm-svn: 105453
-
Jim Grosbach authored
llvm-svn: 105441
-
Bob Wilson authored
VECTOR_SHUFFLEs to REG_SEQUENCE instructions. The standard ISD::BUILD_VECTOR node corresponds closely to REG_SEQUENCE but I couldn't use it here because its operands do not get legalized. That is pretty awful, but I guess it makes sense for other targets. Instead, I have added an ARM-specific version of BUILD_VECTOR that will have its operands properly legalized. This fixes the rest of Radar 7872877. llvm-svn: 105439
-
Bob Wilson authored
Check that all the instructions are in the same basic block, that the EXTRACT_SUBREGs write to the same subregs that are being extracted, and that the source and destination registers are in the same regclass. Some of these constraints can be relaxed with a bit more work. Jakob suggested that the loop that checks for subregs when NewSubIdx != 0 should use the "nodbg" iterator, so I made that change here, too. llvm-svn: 105437
-
Jim Grosbach authored
llvm-svn: 105435
-
Jim Grosbach authored
llvm-svn: 105427
-
- Jun 03, 2010
-
-
Dale Johannesen authored
A temporary flag -arm-tail-calls defaults to off, so there is no functional change by default. Intrepid users may try this; simple cases work but there are bugs. llvm-svn: 105413
-