- Jan 08, 2009
-
-
Dan Gohman authored
llvm-svn: 61950
-
Dan Gohman authored
llvm-svn: 61949
-
Dan Gohman authored
llvm-svn: 61948
-
Dan Gohman authored
llvm-svn: 61947
-
Dale Johannesen authored
functions that don't already have a (dynamic) alloca. Dynamic allocas cause inefficient codegen and we shouldn't propagate this (behavior follows gcc). Two existing tests assumed such inlining would be done; they are hacked by adding an alloca in the caller, preserving the point of the tests. llvm-svn: 61946
-
Duncan Sands authored
day when more linkage types will be handled. llvm-svn: 61944
-
Chris Lattner authored
will get its preferred alignment. It has to be careful and cautiously assume it will just get the ABI alignment. This prevents instcombine from rounding up the alignment of a load/store without adjusting the alignment of the alloca. llvm-svn: 61934
-
Chris Lattner authored
llvm-as: t.ll:2:39: function may not return opaque type %"bwmoyl" = tail call coldcc opaque @g() ^ llvm-svn: 61933
-
Chris Lattner authored
llvm-svn: 61932
-
Chris Lattner authored
llvm-svn: 61931
-
Devang Patel authored
llvm-svn: 61928
-
Misha Brukman authored
* Removed trailing whitespace llvm-svn: 61927
-
Misha Brukman authored
* Removed trailing whitespace llvm-svn: 61926
-
Bill Wendling authored
Some generic clean-ups. Also make the StringMapEntryInitializer specialization apply only to the tests that are actually testing it. llvm-svn: 61923
-
Bill Wendling authored
StringMapEntryInitializer classes. Leave it for the compiler to figure out what the type is and what "0" should be transformed into. * Un-disable the unit tests which test the StringMapEntryInitializer class. llvm-svn: 61922
-
Chris Lattner authored
check242, which invalidates this test. This test is an x86-32 ABI test that is trying to be run in a target-independent way, which is not going to work very well. Just remove the test. llvm-svn: 61921
-
Bill Wendling authored
llvm-svn: 61919
-
Chris Lattner authored
llvm-svn: 61918
-
Chris Lattner authored
llvm-svn: 61917
-
Misha Brukman authored
llvm-svn: 61916
-
Chris Lattner authored
loads from allocas that cover the entire aggregate. This handles some memcpy/byval cases that are produced by llvm-gcc. This triggers a few times in kc++ (with std::pair<std::_Rb_tree_const_iterator <kc::impl_abstract_phylum*>,bool>) and once in 176.gcc (with %struct..0anon). llvm-svn: 61915
-
Misha Brukman authored
* Fixed but in StringMap::clear() * Removed trailing whitespace Original patch by Talin. llvm-svn: 61914
-
Devang Patel authored
Again, shamelessly copied from MMI. llvm-svn: 61912
-
Devang Patel authored
This is a shameless copy of similar APIs from MachineModuleInfo. The copy from MMI will be deleted in near future. llvm-svn: 61908
-
Misha Brukman authored
* Removed trailing whitespace llvm-svn: 61907
-
Misha Brukman authored
llvm-svn: 61906
-
Misha Brukman authored
whitespace. llvm-svn: 61905
-
Misha Brukman authored
llvm-svn: 61904
-
Bob Wilson authored
passed in to this function changed to support multiple return values, leading to some incorrect argument numbers in the failure messages. With this change, the ArgNo values used for return values and parameters are disjoint, and the new IntrinsicParam function translates those ArgNo values to strings that can be used in the messages. This also fixes a few places where PerformTypeCheck did not return false following calls to CheckFailed. llvm-svn: 61903
-
Oscar Fuentes authored
llvm-svn: 61900
-
Bob Wilson authored
odd bit-width vector elements. Add a check in the verifier for this also. llvm-svn: 61899
-
Chris Lattner authored
llvm-svn: 61898
-
Misha Brukman authored
The error was reported by gcc-4.3.0 during compilation. llvm-svn: 61896
-
Gabor Greif authored
llvm-svn: 61895
-
- Jan 07, 2009
-
-
Gabor Greif authored
llvm-svn: 61893
-
Dan Gohman authored
llvm-svn: 61891
-
Dan Gohman authored
llvm-svn: 61890
-
Misha Brukman authored
* Fixed {copy,assignment} constructor test names * s/EXPECT_EQ(true, ...)/ASSERT_TRUE(...)/ Patch by Talin. llvm-svn: 61883
-
Duncan Sands authored
llvm-svn: 61879
-
Duncan Sands authored
was it not very helpful, it was also wrong! The problem is shown in the testcase: the alloca might be passed to a nocapture callee which dereferences it and returns the original pointer. But because it was a nocapture call we think we don't need to track its uses, but we do. llvm-svn: 61876
-