- Nov 04, 2010
-
-
Evan Cheng authored
Fix @llvm.prefetch isel. Selecting between pld / pldw using the first immediate rw. There is currently no intrinsic that matches to pli. llvm-svn: 118237
-
Chris Lattner authored
Right now the code is partitioned but the behavior is the same. This should be improved in the near future. This removes some uses of TheOperandList. llvm-svn: 118232
-
Chris Lattner authored
it doesn't do any lexical stuff anymore. llvm-svn: 118230
-
Chris Lattner authored
llvm-svn: 118228
-
Chris Lattner authored
on the incoming operand list. This also makes the code simpler. llvm-svn: 118225
-
Daniel Dunbar authored
- Primarily useful for running some code with a specified stack size, when pthreads are available. llvm-svn: 118222
-
Jim Grosbach authored
tweaking when we start using it for object file emission or JIT, but it's a start. llvm-svn: 118221
-
Bill Wendling authored
llvm-svn: 118220
-
Chris Lattner authored
llvm-svn: 118219
-
Chris Lattner authored
now matchables contain an explicit list of how to populate each operand in the result instruction instead of having them somehow magically be correlated to the input inst. llvm-svn: 118217
-
Jakob Stoklund Olesen authored
This way, InlineSpiller does the same amount of splitting as the standard spiller. Splitting should really be guided by the register allocator, and doesn't belong in the spiller at all. llvm-svn: 118216
-
Jim Grosbach authored
CodeEmitter. llvm-svn: 118209
-
Jim Grosbach authored
llvm-svn: 118207
-
Jim Grosbach authored
Fixups list for the instruction so the operand encoders can add to it as needed. llvm-svn: 118206
-
Owen Anderson authored
This is both the conceptually correct place for it, as well as allowing it to be more aggressive. llvm-svn: 118204
-
- Nov 03, 2010
-
-
Owen Anderson authored
We could be more aggressive about making this work for a larger range of constants, but this seems like a good start. llvm-svn: 118201
-
Jim Grosbach authored
llvm-svn: 118199
-
Eric Christopher authored
just do it earlier too. llvm-svn: 118195
-
Jakob Stoklund Olesen authored
splitting needs them. llvm-svn: 118194
-
Jakob Stoklund Olesen authored
llvm-svn: 118193
-
Eric Christopher authored
llvm-svn: 118192
-
Chris Lattner authored
llvm-svn: 118190
-
Evan Cheng authored
llvm-svn: 118187
-
Owen Anderson authored
all of the different element sizes are pseudo instructions that map down to vext.8 underneath, with the immediate shifted left to reflect the increased element size. llvm-svn: 118183
-
Dale Johannesen authored
on non-X86 hosts. Hopefully fixes ppc-host buildbot. llvm-svn: 118182
-
Bob Wilson authored
llvm-svn: 118176
-
Bob Wilson authored
For NEON we had been assuming this was always an immediate constant. llvm-svn: 118175
-
Mikhail Glushenkov authored
Makes it more clear that it is just a path manipulation function. llvm-svn: 118174
-
Mikhail Glushenkov authored
llvm-svn: 118173
-
Duncan Sands authored
the code more self-documenting. llvm-svn: 118171
-
Duncan Sands authored
with a SimpleValueType, while an EVT supports equality and inequality comparisons with SimpleValueType. llvm-svn: 118169
-
Duncan Sands authored
llvm-svn: 118168
-
Duncan Sands authored
value type, so there is no point in passing it around using an EVT. Use the simpler MVT everywhere. Rather than trying to propagate this information maximally in all the code that using the calling convention stuff, I chose to do a mainly low impact change instead. llvm-svn: 118167
-
Eric Christopher authored
this by using an undef as a pointer. Fixes rdar://8625016 llvm-svn: 118164
-
Duncan Sands authored
llvm-svn: 118163
-
Evan Cheng authored
Fix preload instruction isel. Only v7 supports pli, and only v7 with mp extension supports pldw. Add subtarget attribute to denote mp extension support and legalize illegal ones to nothing. llvm-svn: 118160
-
-
Bill Wendling authored
llvm-svn: 118151
-
Eric Christopher authored
easier to read. llvm-svn: 118148
-
Bill Wendling authored
vldr.64 d1, [r0, #-32] The problem was with how the addressing mode 5 encodes the offsets. This change makes sure that the way offsets are handled in addressing mode 5 is consistent throughout the MC code. It involves re-refactoring the "getAddrModeImmOpValue" method into an "Imm12" and "addressing mode 5" version. But not to worry! The majority of the duplicated code has been unified. llvm-svn: 118144
-