their corresponding exact-width type. 

llvm-svn: 89224

and @implementation declarations.

llvm-svn: 89223

llvm-svn: 89222

__INTMAX_WIDTH__.

llvm-svn: 89221

implementation mismatch in their qualifiers only.
This will match similar behavior in c/c++ and
fixes radar 7211653.

llvm-svn: 89220

llvm-svn: 89219

llvm-svn: 89218

lack of viable convesion functions.

llvm-svn: 89216

llvm-svn: 89215

llvm-svn: 89214

when LiveVariables is available.

The -split-phi-edges is now gone, and so is the hack to disable it when using
the local register allocator. The PHIElimination pass no longer has
LiveVariables as a prerequisite - that is what broke the local allocator.
Instead we do critical edge splitting when possible - that is when
LiveVariables is available.

llvm-svn: 89213

into a string).

llvm-svn: 89212

Clang.

llvm-svn: 89211

llvm-svn: 89210

@implementation, and in the declaration of the superclass of an
@interface.

llvm-svn: 89207

llvm-svn: 89205

llvm-svn: 89204

stdint.h.

llvm-svn: 89203

llvm-svn: 89201

llvm-svn: 89199

llvm-svn: 89198

llvm-svn: 89197

llvm-svn: 89196

llvm-svn: 89195

llvm-svn: 89194

llvm-svn: 89193

llvm-svn: 89192

llvm-svn: 89191

llvm-svn: 89190

llvm-svn: 89188

contents of the block to be duplicated.  Use this for ARM Cortex A8/9 to
be more aggressive tail duplicating indirect branches, since it makes it
much more likely that they will be predicted in the branch target buffer.
Testcase coming soon.

llvm-svn: 89187

llvm-svn: 89186

llvm-svn: 89185

two classes, one for typenames and one for values;  this seems to have some
support from Doug if not necessarily from the extremely-vague-on-this-point
standard.  Track the location of the 'typename' keyword in a using-typename
decl.  Make a new lookup result for unresolved values and deal with it in
most places.

llvm-svn: 89184

llvm-svn: 89183

llvm-svn: 89182

llvm-svn: 89181

operator->.

llvm-svn: 89180

llvm-svn: 89179

This is probably not confined to *just* these two things.

Anyway, the llvm-gcc front-end may look up the structure layout information for
an abstract type. That information will be stored into a table with the FE's
TD. Instruction combine can come along and also ask for information on that
abstract type, but for a separate TD (the one associated with the pass manager).

After the type is refined, the old structure layout information in the pass
manager's TD file is out of date. If a new type is allocated in the same space
as the old-unrefined type, then the structure type information in the pass
manager's TD file will be wrong, but won't know it.

Fix this by making the TD's structure type information an abstract type user.

llvm-svn: 89176