- Jan 08, 2009
-
-
Fariborz Jahanian authored
gen issue fix. llvm-svn: 61901
-
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
-
-
Ted Kremenek authored
llvm-svn: 61894
-
Gabor Greif authored
llvm-svn: 61893
-
Dan Gohman authored
llvm-svn: 61891
-
Dan Gohman authored
llvm-svn: 61890
-
Ted Kremenek authored
llvm-svn: 61888
-
Douglas Gregor authored
llvm-svn: 61886
-
Douglas Gregor authored
Fix printing of member references to avoid displaying implicitly-generated member references, e.g., for anonymous struct/unions or implicit 'this' in member functions llvm-svn: 61885
-
Misha Brukman authored
* Fixed {copy,assignment} constructor test names * s/EXPECT_EQ(true, ...)/ASSERT_TRUE(...)/ Patch by Talin. llvm-svn: 61883
-
Fariborz Jahanian authored
of category implementation is undeclared. Issue error instead. llvm-svn: 61882
-
Fariborz Jahanian authored
method on 'super' receiver in a category implementation. Other simpler cases were working by accident. llvm-svn: 61880
-
Duncan Sands authored
llvm-svn: 61879
-
Douglas Gregor authored
Duplicate-member checking within classes is still a little messy, and anonymous unions are still completely broken in C. We'll need to unify the handling of fields in C and C++ to make this code applicable in both languages. llvm-svn: 61878
-
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
-
Oscar Fuentes authored
Based on a bug report by Yonggang Luo. llvm-svn: 61875
-
Duncan Sands authored
llvm-svn: 61873
-
Duncan Sands authored
llvm-svn: 61872
-
Daniel Dunbar authored
"fake" options, allowing Tools to be oblivious to whether an argument is real or synthetic. This kills off DerivedArg & a number of FIXMEs. llvm-svn: 61871
-
Duncan Sands authored
llvm-svn: 61870
-
Daniel Dunbar authored
instances; this just complicated things and doesn't seem to provide any benefit. llvm-svn: 61869
-
Steve Naroff authored
Add ObjCContainerDecl class and have ObjCInterfaceDecl/ObjCCategoryDecl/ObjCProtocolDecl inherit from it. llvm-svn: 61866
-
Douglas Gregor authored
Use DeclContext::getLookupContext wherever necessary to ensure that we look through transparent contexts llvm-svn: 61861
-
Douglas Gregor authored
llvm-svn: 61860
-
Chris Lattner authored
integer to a (transitive) bitcast the alloca and if that integer has the full size of the alloca, then it clobbers the whole thing. Handle this by extracting pieces out of the stored integer and filing them away in the SROA'd elements. This triggers fairly frequently because the CFE uses integers to pass small structs by value and the inliner exposes these. For example, in kimwitu++, I see a bunch of these with i64 stores to "%struct.std::pair<std::_Rb_tree_const_iterator<kc::impl_abstract_phylum*>,bool>" In 176.gcc I see a few i32 stores to "%struct..0anon". In the testcase, this is a difference between compiling test1 to: _test1: subl $12, %esp movl 20(%esp), %eax movl %eax, 4(%esp) movl 16(%esp), %eax movl %eax, (%esp) movl (%esp), %eax addl 4(%esp), %eax addl $12, %esp ret vs: _test1: movl 8(%esp), %eax addl 4(%esp), %eax ret The second half of this will be to handle loads of the same form. llvm-svn: 61853
-
Chris Lattner authored
llvm-svn: 61852
-
Chris Lattner authored
change. llvm-svn: 61851
-
Chris Lattner authored
requerying it all over the place. llvm-svn: 61850
-
Chris Lattner authored
code, no functionality change. llvm-svn: 61849
-
Douglas Gregor authored
out its lookup context (to see through linkage specifications). Addresses <rdar://problem/6477142>. llvm-svn: 61848
-
Evan Cheng authored
The coalescer does not coalesce a virtual register to a physical register if any of the physical register's sub-register live intervals overlaps with the virtual register. This is overly conservative. It prevents a extract_subreg from being coalesced away: v1024 = EDI // not killed = = EDI One possible solution is for the coalescer to examine the sub-register live intervals in the same manner as the physical register. Another possibility is to examine defs and uses (when needed) of sub-registers. Both solutions are too expensive. For now, look for "short virtual intervals" and scan instructions to look for conflict instead. This is a small win on x86-64. e.g. It shaves 403.gcc by ~80 instructions. llvm-svn: 61847
-
Daniel Dunbar authored
(for killing off DerivedArg). llvm-svn: 61846
-
Chris Lattner authored
llvm-svn: 61845
-
Daniel Dunbar authored
the ArgList. llvm-svn: 61844
-
Ted Kremenek authored
llvm-svn: 61843
-
Dan Gohman authored
into their left operand, rather than their right. Do this by commuting the operands and inverting the condition. llvm-svn: 61842
-