- Dec 03, 2008
-
-
Dan Gohman authored
parts, and add target-independent code to add/preserve MachineMemOperands. llvm-svn: 60488
-
Dan Gohman authored
llvm-svn: 60487
-
Duncan Sands authored
a new node if the node was actually remapped. llvm-svn: 60482
-
Rafael Espindola authored
Print a single parameter .file directive if we have an ELF target. llvm-svn: 60480
-
Dan Gohman authored
is set but mayLoad is not set. Fix all the problems this turned up. Change code to not use isSimpleLoad instead of mayLoad unless it really wants isSimpleLoad. llvm-svn: 60459
-
- Dec 02, 2008
-
-
Evan Cheng authored
1. ppcf128 select is expanded to f64 select's. 2. f64 select operand 0 is an i1 truncate, it's promoted to i32 zero_extend. 3. f64 select is updated. It's changed back to a "NewNode" and being re-analyzed. 4. f64 select operands are being processed. Operand 0 is a "NewNode". It's being expunged out of ReplacedValues map. 5. ExpungeNode tries to remap f64 select and notice it's a "NewNode" and assert. Duncan, please take a look. Thanks. llvm-svn: 60443
-
Scott Michel authored
consistent with the way it's generally done in other places. llvm-svn: 60439
-
Dan Gohman authored
llvm-svn: 60434
-
Owen Anderson authored
llvm-svn: 60433
-
Dale Johannesen authored
llvm-svn: 60432
-
Tilmann Scheller authored
llvm-svn: 60409
-
Mon P Wang authored
llvm-svn: 60406
-
Evan Cheng authored
llvm-svn: 60392
-
Dale Johannesen authored
llvm-svn: 60391
-
Bill Wendling authored
llvm-svn: 60381
-
- Dec 01, 2008
-
-
Duncan Sands authored
MERGE_VALUES node with only one operand, so get rid of special code that only existed to handle that possibility. llvm-svn: 60349
-
Duncan Sands authored
ReplaceNodeResults: rather than returning a node which must have the same number of results as the original node (which means mucking around with MERGE_VALUES, and which is also easy to get wrong since SelectionDAG folding may mean you don't get the node you expect), return the results in a vector. llvm-svn: 60348
-
- Nov 30, 2008
-
-
Eli Friedman authored
as unsigned divisions. Same caveats as before. llvm-svn: 60284
-
Eli Friedman authored
multiplies. Some more cleverness would be nice, though. It would be nice if we could do this transformation on illegal types. Also, we would prefer a narrower constant when possible so that we can use a narrower multiply, which can be cheaper. llvm-svn: 60283
-
Eli Friedman authored
nearby FIXME. I'm not sure what the right way to fix the Cell test was; if the approach I used isn't okay, please let me know. llvm-svn: 60277
-
- Nov 27, 2008
-
-
Nick Lewycky authored
Despite changing the order of evaluation, this doesn't actually change the meaning of the statement. llvm-svn: 60177
-
Sanjiv Gupta authored
llvm-svn: 60149
-
Evan Cheng authored
llvm-svn: 60141
-
Dale Johannesen authored
llvm-svn: 60137
-
- Nov 26, 2008
-
-
Sanjiv Gupta authored
llvm-svn: 60102
-
Dan Gohman authored
and the LiveInterval.h top-level comment and accordingly. This fixes blocks having spurious live-in registers in boundary cases. llvm-svn: 60092
-
- Nov 25, 2008
-
-
Bill Wendling authored
llvm-svn: 60043
-
Dan Gohman authored
llvm-svn: 60041
-
Bill Wendling authored
llvm-svn: 60016
-
Bill Wendling authored
llvm-svn: 60015
-
Bill Wendling authored
if the operands have the same sign and the sum has sign opposite to that of the operands." llvm-svn: 60014
-
Dan Gohman authored
introduce any new spilling; it just uses unused registers. Refactor the SUnit topological sort code out of the RRList scheduler and make use of it to help with the post-pass scheduler. llvm-svn: 59999
-
- Nov 24, 2008
-
-
Bill Wendling authored
- Mark "add with overflow" as having a custom lowering for X86. Give it a null lowering representation for now. llvm-svn: 59971
-
Dan Gohman authored
to removePred because an SUnit can both data-depend and anti-depend on the same SUnit. llvm-svn: 59969
-
Dan Gohman authored
llvm-svn: 59968
-
Dan Gohman authored
obscure tail-merging opportunities. llvm-svn: 59967
-
Matthijs Kooijman authored
llvm-svn: 59961
-
Duncan Sands authored
(this doesn't happen that often, since most code does not use illegal types) then follow it by a DAG combiner run that is allowed to generate illegal operations but not illegal types. I didn't modify the target combiner code to distinguish like this between illegal operations and illegal types, so it will not produce illegal operations as well as not producing illegal types. llvm-svn: 59960
-
Evan Cheng authored
llvm-svn: 59952
-
Bill Wendling authored
llvm-svn: 59926
-