- Sep 08, 2008
-
-
Dan Gohman authored
llvm-svn: 55919
-
Dan Gohman authored
llvm-svn: 55918
-
Dan Gohman authored
llvm-svn: 55917
-
Dan Gohman authored
llvm-svn: 55915
-
Devang Patel authored
llvm-svn: 55913
-
Duncan Sands authored
callgraph is printed. llvm-svn: 55912
-
Evan Cheng authored
llvm-svn: 55911
-
Anton Korobeynikov authored
llvm-svn: 55904
-
Anton Korobeynikov authored
llvm-svn: 55901
-
Anton Korobeynikov authored
llvm-svn: 55900
-
Anton Korobeynikov authored
llvm-svn: 55899
-
Anton Korobeynikov authored
llvm-svn: 55898
-
Duncan Sands authored
llvm-svn: 55896
-
Duncan Sands authored
llvm-svn: 55895
-
Duncan Sands authored
long as the callgraph is correct. It checks for wrong callgraphs more strictly. llvm-svn: 55894
-
Evan Cheng authored
llvm-svn: 55892
-
Evan Cheng authored
llvm-svn: 55891
-
Bill Wendling authored
before. This is taken care of in the selection DAG pass. In my opinion, this should be in one place or the other. I.e., it should probably be removed from the DAG combiner (along with the other arithmetic transformations on constants that are essentially no-ops). llvm-svn: 55889
-
- Sep 07, 2008
-
-
Bill Wendling authored
// fold (sub c1, c2) -> c1-c2 from a no-op into an actual transformation. llvm-svn: 55886
-
Duncan Sands authored
llvm-svn: 55883
-
Evan Cheng authored
Initial fastisel call support for C, Fast, and X86_FastCall calling conventions. It's meant to handle "simple" calls, i.e. no byval, structret, etc. It doesn't support multi-result returns either. Not yet turned on, it needs to support sext / zext of arguments and result. llvm-svn: 55882
-
Evan Cheng authored
llvm-svn: 55881
-
Evan Cheng authored
llvm-svn: 55880
-
Evan Cheng authored
- Add a AnalyzeCallResult specialized for calls which produce a single value. This is used by fastisel. llvm-svn: 55879
-
Evan Cheng authored
llvm-svn: 55877
-
- Sep 06, 2008
-
-
Nuno Lopes authored
this pass doesnt seem to be used, but still it's now a little more correct llvm-svn: 55873
-
Duncan Sands authored
call (thus changing the call site) it didn't inform the callgraph about this. But the call site does matter - as shown by the testcase, the callgraph become invalid after the inliner ran (with an edge between two functions simply missing), resulting in wrong deductions by GlobalsModRef. llvm-svn: 55872
-
Owen Anderson authored
llvm-svn: 55868
-
Owen Anderson authored
llvm-svn: 55867
-
Dale Johannesen authored
llvm-svn: 55866
-
Owen Anderson authored
llvm-svn: 55865
-
Eli Friedman authored
i32>. This is a little messy, but it works. We should really get rid of the intrinsics, though, since they map perfectly well to standard LLVM instructions. llvm-svn: 55864
-
Dan Gohman authored
out of ScheduleDAGEmit.cpp and into SelectionDAGISel.cpp. This allows it to be run exactly once per function, even if multiple SelectionDAG iterations happen in the entry block, as may happen with FastISel. llvm-svn: 55863
-
- Sep 05, 2008
-
-
Devang Patel authored
llvm-svn: 55861
-
Duncan Sands authored
because it does not maintain a correct list of callsites. I discovered (see following commit) that the inliner will create a wrong callgraph if it is fed a callgraph with correct edges but incorrect callsites. These were created by Prune-EH, and while it wasn't done via removeCallEdgeTo, it could have been done via removeCallEdgeTo, which is an accident waiting to happen. Use removeCallEdgeFor instead. llvm-svn: 55859
-
Dan Gohman authored
llvm-svn: 55857
-
Dale Johannesen authored
llvm-svn: 55856
-
Dan Gohman authored
llvm-svn: 55855
-
Evan Cheng authored
llvm-svn: 55854
-
Owen Anderson authored
llvm-svn: 55853
-