llvm-svn: 119069

llvm-svn: 119068

llvm-svn: 119067

llvm-svn: 119066

this fixes 3 more ppc tests.

llvm-svn: 119065

llvm-svn: 119064

failures in CodeGen/PowerPC from 120 -> 117

llvm-svn: 119063

add support for darwin vs aix syntax.  We now can print instructions
like this:

	add r3, r3, r4
	blr 

and (in aix mode):
	add 3, 3, 4
	blr 

llvm-svn: 119062

instprinter when -enable-ppc-inst-printer is passed to llc.

llvm-svn: 119061

llvm-svn: 119060

llvm-svn: 119059

llvm-svn: 119058

looking for lib/Target/*AsmPrinter.cpp.  Fix llvm-config to handle targets
that don't have an explicit AsmPrinter library.

llvm-svn: 119057

that should be split out is the InstPrinter (if a target is mc'ized).
This change makes all the targets be consistent.

llvm-svn: 119056

it to get better phi node simplification.

llvm-svn: 119055

llvm-svn: 119054

llvm-svn: 119053

llvm-svn: 119052

and the Alpha backend isn't MCized yet.  Approved by Andrew.

llvm-svn: 119051

llvm-svn: 119050

llvm-svn: 119049

llvm-svn: 119048

the Stmt* visitation in CursorVisitor to be
data-recursive.

Since AnnotationTokensWorker explicitly calls
CursorVisitor::VisitChildren(), it essentially
transforms the data-recursive algorithm in
CursorVisitor back into a non-data recursive one.
This is particularly bad because the data-recursive
algorithm uses more stack space per stack frame,
which can cause us to blow the stack in some cases.

"Fix" this by making the stack that AnnotationTokensWorker
runs in really huge.  The real fix is to modify
AnnotationTokensWorker not to do the explicit
recursive call.

llvm-svn: 119047

'LangOptionsBase' that default initializes all flags to 0.  Now the ctor of LangOptions
only initializes the flags that might be non-zero (significantly simplifying things).

This also appeases Valgrind on Mac OS X, which no longer reports that one of the flags
may be uninitialized.

llvm-svn: 119045

Elidable CXXConstructExpr should inhibit calling destructor for temporary 
that is copied, not the one created. This is because eliding copy constructor 
means that the object that was to be copied will be constructed directly in 
memory the copy would be constructed in.

llvm-svn: 119044

offload the work to hasConstantValue rather than do something more
complicated (such handling mutually recursive phis) because (1) it is
not clear it is worth it; and (2) if it is worth it, maybe such logic
would be better placed in hasConstantValue.  Adjust some GVN tests
which are now cleaned up much further (eg: all phi nodes are removed).

llvm-svn: 119043

operands are the phi node itself or undef, then return undef.
This logic already existed at a higher level so in practice it
shouldn't make the slightest difference.  Note that this code
could be replaced by a call to PN->hasConstantValue().  However
since we bail out the moment we see a non-constant operand, it
is more efficient to have a specialized version of that logic.

llvm-svn: 119041

llvm-svn: 119040

llvm-svn: 119038

Return the result of a complex assignment with the original values,
not by performing a load from the l-value;  this is the correct
semantics in C, although not in C++.

llvm-svn: 119037

implicit conversions;  the last batch was specific to promotions.
I think this is the full set we need.  I do think dividing the cast
kinds into floating and integral is probably a good idea.

Annotate a *lot* more C casts with useful cast kinds.

llvm-svn: 119036

llvm-svn: 119035

llvm-svn: 119034

llvm-svn: 119033

llvm-svn: 119032

llvm-svn: 119031

covered by the normal recursive visitation.

llvm-svn: 119030

llvm-svn: 119029

llvm-svn: 119028

somehow got several block tests fail with a linux built
compiler.

llvm-svn: 119027