- Sep 16, 2008
-
-
Dan Gohman authored
of r56230, r56232, and r56246. llvm-svn: 56247
-
Dan Gohman authored
- Recognize expressions like "x > -1 ? x : 0" as min/max and turn them into expressions like "x < 0 ? 0 : x", which is easily recognizable as a min/max operation. - Refrain from folding expression like "y/2 < 1" to "y < 2" when the comparison is being used as part of a min or max idiom, like "y/2 < 1 ? 1 : y/2". In that case, the division has another use, so folding doesn't eliminate it, and obfuscates the min/max, making it harder to recognize as a min/max operation. These benefit ScalarEvolution, CodeGen, and anything else that wants to recognize integer min and max. llvm-svn: 56246
-
Evan Cheng authored
llvm-svn: 56244
-
Dan Gohman authored
llvm-svn: 56243
-
Bill Wendling authored
"declare" statement. llvm-svn: 56241
-
Bill Wendling authored
llvm-svn: 56240
-
Dan Gohman authored
are not enabled. Instead just omit the tail call flag when calls are created. llvm-svn: 56235
-
Dan Gohman authored
SCEV-whitespace changes. llvm-svn: 56234
-
Dan Gohman authored
bitcode reader/writer as follows: - add and use new bitcode FUNC_CODE_INST_VSELECT to handle the llvm select opcode using either i1 or [N x i1] as the selector. - retain old BITCODE FUNC_CODE_INST_SELECT in the bitcode reader to handle select on i1 for backwards compatibility with existing bitcode files. - re-enable the vector-select.ll test program. Also, rename the recently added bitcode opcode FUNC_CODE_INST_VCMP to FUNC_CODE_INST_CMP2 and make the bitcode writer use it to handle fcmp/icmp on scalars or vectors. In the bitcode writer, use FUNC_CODE_INST_CMP for vfcmp/vicmp only. In the bitcode reader, have FUNC_CODE_INST_CMP handle icmp/fcmp returning bool, for backwards compatibility with existing bitcode files. Patch by Preston Gurd! llvm-svn: 56233
-
Dan Gohman authored
an if statement that guards a loop, to allow indvars to avoid smax operations in more situations. llvm-svn: 56232
-
Owen Anderson authored
Live intervals for live-in registers should begin at the beginning of a basic block, not at the first instruction. Also, their valno's should have an unknown def. This has no effect currently, but was causing issues when StrongPHIElimination was enabled. llvm-svn: 56231
-
- Sep 15, 2008
-
-
Dan Gohman authored
cases. See the comment above OptimizeSMax for the full story, and the testcase for an example. This cancels out a pessimization commonly attributed to indvars, and will allow us to lift some of the artificial throttles in indvars, rather than add new ones. llvm-svn: 56230
-
Devang Patel authored
This can be used by other stand alone tools, such as 'opt'. llvm-svn: 56229
-
Bruno Cardoso Lopes authored
http://llvm.org/bugs/show_bug.cgi?id=2751 Abicall was enabled even when static code model was provided in the command line. The correct behavior is to disable abicall when static is specified. llvm-svn: 56228
-
Dan Gohman authored
libcalls, as in this testcase on ARM. llvm-svn: 56226
-
Bruno Cardoso Lopes authored
llvm-svn: 56225
-
Duncan Sands authored
llvm-svn: 56222
-
Dan Gohman authored
x86_ssecallcc, function notes, and some whitespace adjustments. llvm-svn: 56221
-
Nick Lewycky authored
block specified by the InstList. Patch by Stefanus Du Toit. llvm-svn: 56200
-
Evan Cheng authored
Correctly update kill infos after extending a live range and merge 2 val#'s; fix 56165 - do not mark val# copy field if the copy does not define the val#. llvm-svn: 56199
-
Nick Lewycky authored
This fixes part of PR2793. llvm-svn: 56198
-
- Sep 14, 2008
-
-
Dan Gohman authored
its callers to emit a space character before calling it when a space is needed. This fixes several spurious whitespace issues in ScalarEvolution's debug dumps. See the test changes for examples. This also fixes odd space-after-tab indentation in the output for switch statements, and changes calls from being printed like this: call void @foo( i32 %x ) to this: call void @foo(i32 %x) llvm-svn: 56196
-
Dale Johannesen authored
llvm-svn: 56194
-
- Sep 13, 2008
-
-
Gabor Greif authored
llvm-svn: 56190
-
Dan Gohman authored
isImmediate(), isRegister(), and friends, to avoid confusion about having two different names with the same meaning. I'm not attached to the longer names, and would be ok with changing to the shorter names if others prefer it. llvm-svn: 56189
-
Duncan Sands authored
Treat stores as reading memory, just to play safe. llvm-svn: 56188
-
Evan Cheng authored
llvm-svn: 56184
-
Dan Gohman authored
Currently it just holds the calling convention and flags for isVarArgs and isTailCall. And it has several utility methods, which eliminate magic 5+2*i and similar index computations in several places. CallSDNodes are not CSE'd. Teach UpdateNodeOperands to handle nodes that are not CSE'd gracefully. llvm-svn: 56183
-
Evan Cheng authored
llvm-svn: 56182
-
Evan Cheng authored
llvm-svn: 56181
-
Evan Cheng authored
llvm-svn: 56180
-
Evan Cheng authored
llvm-svn: 56179
-
Evan Cheng authored
llvm-svn: 56178
-
Evan Cheng authored
llvm-svn: 56176
-
Evan Cheng authored
llvm-svn: 56172
-
Evan Cheng authored
llvm-svn: 56171
-
- Sep 12, 2008
-
-
Duncan Sands authored
llvm-svn: 56170
-
Evan Cheng authored
vr2 = OR vr0, vr1 => vr2 = OR vr1, vr1 // after coalescing vr0 with vr1 Update the value# of the destination register with the copy instruction if that happens. llvm-svn: 56165
-
Dan Gohman authored
ConstantFP* instead of APInt and APFloat directly. This reduces the amount of time to create ConstantSDNode and ConstantFPSDNode nodes when ConstantInt* and ConstantFP* respectively are already available, as is the case in SelectionDAGBuild.cpp. Also, it reduces the amount of time to legalize constants into constant pools, and the amount of time to add ConstantFP operands to MachineInstrs, due to eliminating ConstantInt::get and ConstantFP::get calls. It increases the amount of work needed to create new constants in cases where the client doesn't already have a ConstantInt* or ConstantFP*, such as legalize expanding 64-bit integer constants to 32-bit constants. And it adds a layer of indirection for the accessor methods. But these appear to be outweight by the benefits in most cases. It will also make it easier to make ConstantSDNode and ConstantFPNode more consistent with ConstantInt and ConstantFP. llvm-svn: 56162
-
Dale Johannesen authored
representation; coalescer and RA need to know about it. No functional change. llvm-svn: 56161
-