- Jun 06, 2009
-
-
Eli Friedman authored
integer type to be consistent with normal operation legalization. No visible change because nothing is actually using this at the moment. llvm-svn: 72980
-
Devang Patel authored
llvm-svn: 72970
-
Dan Gohman authored
llvm-svn: 72969
-
Devang Patel authored
llvm-svn: 72965
-
- Jun 05, 2009
-
-
Devang Patel authored
Update code generator to use this attribute and remove NoImplicitFloat target option. Update llc to set this attribute when -no-implicit-float command line option is used. llvm-svn: 72959
-
Nate Begeman authored
build vectors with i64 elements will only appear on 32b x86 before legalize. Since vector widening occurs during legalize, and produces i64 build_vector elements, the dag combiner is never run on these before legalize splits them into 32b elements. Teach the build_vector dag combine in x86 back end to recognize consecutive loads producing the low part of the vector. Convert the two uses of TLI's consecutive load recognizer to pass LoadSDNodes since that was required implicitly. Add a testcase for the transform. Old: subl $28, %esp movl 32(%esp), %eax movl 4(%eax), %ecx movl %ecx, 4(%esp) movl (%eax), %eax movl %eax, (%esp) movaps (%esp), %xmm0 pmovzxwd %xmm0, %xmm0 movl 36(%esp), %eax movaps %xmm0, (%eax) addl $28, %esp ret New: movl 4(%esp), %eax pmovzxwd (%eax), %xmm0 movl 8(%esp), %eax movaps %xmm0, (%eax) ret llvm-svn: 72957
-
Evan Cheng authored
Changing allocation ordering from r3 ... r0 back to r0 ... r3. The order change no longer make sense after the coalescing changes we have made since then. llvm-svn: 72955
-
Devang Patel authored
llvm-svn: 72954
-
Dan Gohman authored
llvm-svn: 72953
-
Evan Cheng authored
llvm-svn: 72952
-
Evan Cheng authored
llvm-svn: 72950
-
Dan Gohman authored
llvm-svn: 72949
-
Dan Gohman authored
llvm-svn: 72948
-
Dan Gohman authored
llvm-svn: 72946
-
Sanjiv Gupta authored
llvm-svn: 72942
-
Sanjiv Gupta authored
llvm-svn: 72941
-
Bruno Cardoso Lopes authored
MachO Writer. This will change with the arrival of ObjectCodeEmitter and BinaryObject llvm-svn: 72906
-
Dan Gohman authored
a few lines later on. llvm-svn: 72904
-
Bill Wendling authored
`-fomit-frame-pointer', we would lack the DW_CFA_advance_loc information for a lot of function, and then they would be `0'. The linker (at least on Darwin) needs to encode the stack size. In some cases, the stack size is too large to directly encode. So the linker checks to see if there is a "subl $xxx,%esp" instruction at the point where the `DW_CFA_def_cfa_offset' says the pc was. If so, the compact encoding records the offset in the function to where the stack size is embedded. But because the `DW_CFA_advance_loc' instructions are missing, it looks before the function and dies. So, instead of emitting the EH debug label before the stack adjustment operations, emit it afterwards, right before the frame move stuff. llvm-svn: 72898
-
Dan Gohman authored
integer and floating-point opcodes, introducing FAdd, FSub, and FMul. For now, the AsmParser, BitcodeReader, and IRBuilder all preserve backwards compatability, and the Core LLVM APIs preserve backwards compatibility for IR producers. Most front-ends won't need to change immediately. This implements the first step of the plan outlined here: http://nondot.org/sabre/LLVMNotes/IntegerOverflow.txt llvm-svn: 72897
-
Devang Patel authored
Update code generator to use this attribute and remove DisableRedZone target option. Update llc to set this attribute when -disable-red-zone command line option is used. llvm-svn: 72894
-
- Jun 04, 2009
-
-
Dale Johannesen authored
using Promote which won't work because i64 isn't a legal type. It's easy enough to use Custom, but then we have the problem that when the type legalizer is promoting FP_TO_UINT->i16, it has no way of telling it should prefer FP_TO_SINT->i32 to FP_TO_UINT->i32. I have uncomfortably hacked this by making the type legalizer choose FP_TO_SINT when both are Custom. This fixes several regressions in the testsuite. llvm-svn: 72891
-
Evan Cheng authored
RALinScan::attemptTrivialCoalescing() was returning a virtual register instead of the physical register it is allocated to. This resulted in virtual register(s) being added the live-in sets. llvm-svn: 72890
-
Evan Cheng authored
A value defined by an implicit_def can be liven to a use BB. This is unfortunate. But register allocator still has to add it to the live-in set of the use BB. llvm-svn: 72889
-
Lang Hames authored
llvm-svn: 72880
-
Dan Gohman authored
instcombine doesn't know when it's safe. To partially compensate for this, introduce new code to do this transformation in dagcombine, which can use UnsafeFPMath. llvm-svn: 72872
-
Dan Gohman authored
llvm-svn: 72870
-
Sanjiv Gupta authored
llvm-svn: 72866
-
Sanjiv Gupta authored
llvm-svn: 72861
-
Torok Edwin authored
llvm-svn: 72858
-
Torok Edwin authored
llvm-svn: 72854
-
Eli Friedman authored
the code tried to use "push", which doesn't exist for XMM registers.) llvm-svn: 72836
-
Eli Friedman authored
llvm-svn: 72830
-
Dan Gohman authored
llvm-svn: 72828
-
Evan Cheng authored
Re-apply 72756 with fixes. One of those was introduced by we changed MachineInstrBuilder::addReg() interface. llvm-svn: 72826
-
Lang Hames authored
llvm-svn: 72825
-
Bruno Cardoso Lopes authored
llvm-svn: 72821
-
Stuart Hastings authored
llvm-svn: 72817
-
- Jun 03, 2009
-
-
Stuart Hastings authored
llvm-svn: 72808
-
Evan Cheng authored
For Darwin / x86_64, override -relocation-model=static to pic if the output is assembly since Darwin assembler does not really support -static codeine. I view this as a temporary workaround until the assembler / linker changes. llvm-svn: 72806
-