instead of returning it in an std::string.  Based on this change:

1. Change TargetLoweringObjectFileCOFF::getCOFFSection to take a StringRef
2. Change a bunch of targets to call makeNameProper with a smallstring,
   making several of them *much* more efficient.
3. Rewrite Mangler::makeNameProper to not build names and then prepend
   prefixes, not use temporary std::strings, and to avoid other crimes.

llvm-svn: 93298

llvm-svn: 93297

llvm-svn: 93296

llvm-svn: 93295

llvm-svn: 93294

llvm-svn: 93293

llvm-svn: 93292

integers on 64-bit systems.

llvm-svn: 93291

llvm-svn: 93290

Revert 93270 pending investigation of how stray non-constant values end up in ValueEnumerator's ValueList during WriteConstants()

llvm-svn: 93289

llvm-svn: 93288

llvm-svn: 93287

llvm-svn: 93286

llvm-svn: 93285

llvm-svn: 93284

llvm-svn: 93283

clang -cc1 logic for running an action against a set of options.
 - This should make it easier to build tools that have a clang -cc1 like
   interface, but aren't actually part of clang -cc1.

llvm-svn: 93282

llvm-svn: 93281

It was only being used by instructions with the t_addrmode_sp addressing mode,
and that is pattern matched in a way that guarantees SP is used. There is
never any register allocation done from this class.

llvm-svn: 93280

flag doesn't exist there, and this is an x86 test.

llvm-svn: 93279

Add a quick pass to optimize sign / zero extension instructions. For targets where the pre-extension values are available in the subreg of the result of the extension, replace the uses of the pre-extension value with the result + extract_subreg.

For now, this pass is fairly conservative. It only perform the replacement when both the pre- and post- extension values are used in the block. It will miss cases where the post-extension values are live, but not used.

llvm-svn: 93278

why the candidate is non-viable.  There's a lot we can do to improve this, but
it's a good start.  Further improvements should probably be integrated with the
bad-initialization reporting routines.

llvm-svn: 93277

llvm-svn: 93276

Make method definitions in TUVisitor out-of-line, making it easy to tell what visitor methods are defined.
Generalize TUVisitor to take a general "root" and "iterator" callback; this is prep. work to merging TUVisitor and CDeclVisitor.

llvm-svn: 93275

redefined. There's a FIXME with an apology about why we don't try to
do better here. Fixes <rdar://problem/7513023>.

llvm-svn: 93274

dumper doesn't really do what I want yet, but
at least it doesn't crash now.

llvm-svn: 93272

ivar name lookup. Fixes pr5986.

llvm-svn: 93271

llvm-svn: 93270

llvm-svn: 93269

llvm-svn: 93268

Enhance USR generation a bit with support for records.

llvm-svn: 93267

unevaluated contexts, because they only matter for code that will
actually be evaluated at runtime.

As part of this, I had to extend PartialDiagnostic to support fix-it
hints.

llvm-svn: 93266

llvm-svn: 93262

llvm-svn: 93261

llvm-svn: 93260

llvm-svn: 93259

not in an evaluated context.  This removes some bogus warnings.

llvm-svn: 93258

name a template, when they occur in a base-specifier. This is one of
the (few) places where we know for sure that an identifier followed by
a '<' must be a template name, so we can diagnose and recover well:

test/SemaTemplate/dependent-base-classes.cpp:9:16: error: missing
'template'
      keyword prior to dependent template name 'T::apply'
struct X1 : T::apply<U> { }; // expected-error{{missing 'template' ...
               ^
               template 
test/SemaTemplate/dependent-base-classes.cpp:12:13: error: unknown
template name
      'vector'
struct X2 : vector<T> { }; // expected-error{{unknown template name
'vector'}}
            ^
2 diagnostics generated.

llvm-svn: 93257

llvm-svn: 93256

llvm-svn: 93255