- Mar 27, 2007
-
-
Evan Cheng authored
llvm-svn: 35363
-
Dale Johannesen authored
hopefully forestall similar errors. llvm-svn: 35362
-
- Mar 26, 2007
-
-
Evan Cheng authored
llvm-svn: 35350
-
- Mar 25, 2007
-
-
Anton Korobeynikov authored
strategy, emit JT's where possible. llvm-svn: 35338
-
Chris Lattner authored
CodeGen/X86/2007-03-24-InlineAsmVectorOp.ll llvm-svn: 35332
-
Chris Lattner authored
implement initial support for the silly X constraint. Testcase here: CodeGen/X86/2007-03-24-InlineAsmXConstraint.ll llvm-svn: 35327
-
Chris Lattner authored
llvm-svn: 35324
-
Chris Lattner authored
not just the first letter. No functionality change. llvm-svn: 35322
-
- Mar 24, 2007
-
-
Chris Lattner authored
llvm-svn: 35299
-
Evan Cheng authored
llvm-svn: 35293
-
- Mar 23, 2007
-
-
Evan Cheng authored
llvm-svn: 35289
-
Evan Cheng authored
llvm-svn: 35286
-
Evan Cheng authored
1. Address offset is in bytes. 2. Make sure truncate node uses are replaced with new load. llvm-svn: 35274
-
- Mar 22, 2007
-
-
Dan Gohman authored
llvm-svn: 35265
-
Evan Cheng authored
llvm-svn: 35254
-
Evan Cheng authored
where the destination is dead. llvm-svn: 35252
-
- Mar 21, 2007
-
-
Dale Johannesen authored
llvm-svn: 35245
-
Evan Cheng authored
llvm-svn: 35239
-
- Mar 20, 2007
-
-
Evan Cheng authored
llvm-svn: 35228
-
Dale Johannesen authored
instructions (that would have to be split later) llvm-svn: 35227
-
Dale Johannesen authored
llvm-svn: 35226
-
Jeff Cohen authored
llvm-svn: 35224
-
Lauro Ramos Venancio authored
llvm-svn: 35220
-
Evan Cheng authored
llvm-svn: 35219
-
Lauro Ramos Venancio authored
llvm-svn: 35213
-
Evan Cheng authored
llvm-svn: 35208
-
- Mar 19, 2007
-
-
Evan Cheng authored
llvm-svn: 35165
-
Evan Cheng authored
llvm-svn: 35153
-
- Mar 18, 2007
-
-
Evan Cheng authored
- Use distance to closest use to determine whether to abort coalescing. llvm-svn: 35141
-
Evan Cheng authored
llvm-svn: 35140
-
- Mar 17, 2007
-
-
Evan Cheng authored
llvm-svn: 35135
-
Evan Cheng authored
to be really bad. Once they are joined they are not broken apart. Also, physical intervals cannot be spilled! Added a heuristic as a workaround for this. Be careful coalescing with a physical register if the virtual register uses are "far". Check if there are uses in the same loop as the source (copy instruction). Check if it is in the loop preheader, etc. llvm-svn: 35134
-
Evan Cheng authored
llvm-svn: 35133
-
Evan Cheng authored
in that BB. llvm-svn: 35132
-
- Mar 16, 2007
-
-
Evan Cheng authored
llvm-svn: 35127
-
Evan Cheng authored
llvm-svn: 35126
-
Evan Cheng authored
computation used as GEP indexes and if the expression can be folded into target addressing mode of GEP load / store use types. llvm-svn: 35123
-
Evan Cheng authored
folded into target addressing mode for the given type. llvm-svn: 35121
-
- Mar 15, 2007
-
-
Evan Cheng authored
llvm-svn: 35117
-
- Mar 14, 2007
-
-
Evan Cheng authored
it as a late BURR scheduling tie-breaker. Intuitively, it's good to push down instructions whose results are liveout so their long live ranges won't conflict with other values which are needed inside the BB. Further prioritize liveout instructions by the number of operands which are calculated within the BB. llvm-svn: 35109
-