llvm-svn: 54107

llvm-svn: 54106

ASTContext::getCanonicalType instead (PR2189)

llvm-svn: 54105

llvm-svn: 54104

 - Stolen from LLVM with minor modifications

llvm-svn: 54103

of doing it directly.  This is required for PR2189.

llvm-svn: 54102

llvm-svn: 54101

llvm-svn: 54100

llvm-svn: 54099

improve 'expression unused' diagnostics for stmtexprs.

llvm-svn: 54098

llvm-svn: 54097

llvm-svn: 54096

llvm-svn: 54095

last client of the old ParseObjCProtocolReferences, so it also removes it.

llvm-svn: 54094

llvm-svn: 54093

This temporarily duplicates ParseObjCProtocolReferences, but it
will be removed in the future.

llvm-svn: 54092

llvm-svn: 54091

llvm-svn: 54090

llvm-svn: 54089

llvm-svn: 54088

clients allocate the memory and it delete it.

llvm-svn: 54087

1) reject stuff like "id<foo> short" and "<foo> short".  2) set
the declspec range correctly 3) only parse protocol qualifiers
when in objc mode.

llvm-svn: 54086

llvm-svn: 54085

remove the objc- prefix from the tests that use it.

llvm-svn: 54084

First, fix canonical type handling of these, since protocol qualified id's are always
canonical.  Next, enhance SemaType to actually make these when used (instead of int)
allowing them to actually be used when appropriate.  Finally remove a bunch of logic
relating to the mishandling of canonical types with protocol-qual id's.  This fixes
rdar://5986251

llvm-svn: 54083

like "id<foo>".  This 1) fixes an infinite loop in the parser on things
like "short<foo>" 2) emits a warning about this bogus construct and 3)
changes the testcase to be substantially reduced.

llvm-svn: 54082

llvm-svn: 54081

as well as complex float. rdar://6097730

llvm-svn: 54080

llvm-svn: 54079

are important part of control flow structures.

llvm-svn: 54078

Fix the issues originally addressed in r54070.  After thinking about it some more, I realized that the right thing to do
is to have StrongPHIElimination use its knowledge of the PHIs before they're erased to update the intervals appropriate.  This is
both simpler and more accurate than the alternative, which was having LIA figure it out when it renumbered things, plus it's just
the right thing to do!

llvm-svn: 54077

llvm-svn: 54076

llvm-svn: 54075

llvm-svn: 54074

llvm-svn: 54073

llvm-svn: 54072

llvm-svn: 54071

Special cases are needed in renumbering when dealing with renumbering after a PHI has been removed.  The interval previously defined
by the PHI needs to be extended to the beginning of its basic block, and the intervals that were inputs need to be trimmed to the end 
of their basic blocks.

llvm-svn: 54070

llvm-svn: 54069

problem with &&/||.  2) use canonical types for comparison instead 
of raw types. 3) emit an ext-warn for a gnu extension.

Also simplify the code to make it less nested.

llvm-svn: 54068