- Feb 26, 2010
-
-
Jakob Stoklund Olesen authored
This is possible because F8RC is a subclass of F4RC. We keep FMRSD around so fextend has a pattern. Also allow folding of memory operands on FMRSD. llvm-svn: 97275
-
Fariborz Jahanian authored
llvm-svn: 97274
-
Dan Gohman authored
llvm-svn: 97273
-
Dan Gohman authored
llvm-svn: 97271
-
Dan Gohman authored
copied out of the source tree. llvm-svn: 97270
-
Bill Wendling authored
llvm-svn: 97269
-
Chris Lattner authored
llvm-svn: 97268
-
Dan Gohman authored
longer than 80 columns. This replaces the heavy-handed "textwidth" mechanism, and makes the trailing-whitespace highlighting lazy so that it isn't constantly jumping on the user during typing. llvm-svn: 97267
-
Tanya Lattner authored
llvm-svn: 97266
-
Tanya Lattner authored
llvm-svn: 97265
-
Dan Gohman authored
llvm-svn: 97264
-
Dan Gohman authored
llvm-svn: 97263
-
Jakob Stoklund Olesen authored
The PowerPC floating point registers can represent both f32 and f64 via the two register classes F4RC and F8RC. F8RC is considered a subclass of F4RC to allow cross-class coalescing. This coalescing only affects whether registers are spilled as f32 or f64. Spill slots must be accessed with load/store instructions corresponding to the class of the spilled register. PPCInstrInfo::foldMemoryOperandImpl was looking at the instruction opcode which is wrong. X86 has similar floating point register classes, but doesn't try to fold memory operands, so there is no problem there. llvm-svn: 97262
-
Jakob Stoklund Olesen authored
llvm-svn: 97261
-
Jeffrey Yasskin authored
build with exceptions even if LLVM is built without. llvm-svn: 97260
-
Benjamin Kramer authored
llvm-svn: 97259
-
John McCall authored
llvm-svn: 97258
-
Dan Gohman authored
llvm-svn: 97257
-
Dan Gohman authored
llvm-svn: 97256
-
Dale Johannesen authored
as X86 is currently the only FastISel target. Per review. llvm-svn: 97255
-
Fariborz Jahanian authored
Fixes radar 7692350. llvm-svn: 97254
-
-
Dale Johannesen authored
llvm-svn: 97252
-
Dale Johannesen authored
llvm-svn: 97251
-
Ted Kremenek authored
Sema and into analyze_printf::ParseFormatString(). Also use a bitvector to determine what arguments have been covered (instead of just checking to see if the last argument consumed is the max argument). This is prep. for support positional arguments (an IEEE extension). llvm-svn: 97248
-
Bob Wilson authored
argument of createGVNPass and set it automatically for -O3. llvm-svn: 97245
-
Fariborz Jahanian authored
blocks's argument in the inner block requires special treatment. Fixes radar 7692419. llvm-svn: 97244
-
Sanjiv Gupta authored
llvm-svn: 97236
-
Bob Wilson authored
llvm-svn: 97235
-
Chris Lattner authored
stuff to emit optimal nops in the right places. llvm-svn: 97233
-
Sanjiv Gupta authored
present in the module. llvm-svn: 97232
-
Chris Lattner authored
llvm-svn: 97231
-
Jeffrey Yasskin authored
llvm-svn: 97230
-
Jeffrey Yasskin authored
llvm-svn: 97229
-
Sanjiv Gupta authored
llvm-svn: 97228
-
Dan Gohman authored
llvm-svn: 97227
-
Richard Osborne authored
Previously LoopStrengthReduce would sometimes be unable to find a legal formula, causing an assertion failure. llvm-svn: 97226
-
Zhongxing Xu authored
Use this information to find the returned value and bind it to CallExpr in ProcessCallExit. And there is no need to remove dead bindings in ProcessCallExit, because a. it would clean up the return value bound to CallExpr b. we still would do it in the next ProcessStmt(), where we would not misclean up the return value. llvm-svn: 97225
-
Chandler Carruth authored
fix, just trying to get the build bots happy again. llvm-svn: 97223
-
Zhongxing Xu authored
llvm-svn: 97222
-