llvm-svn: 80260

llvm-svn: 80259

llvm-svn: 80258

per the documentation, although I'm not completely sure.

llvm-svn: 80257

llvm-svn: 80256

llvm-svn: 80255

llvm-svn: 80254

templates within class templates, producing a member function template
of a class template specialization. If you can parse that, I'm
sorry. Example:

  template<typename T>
  struct X {
    template<typename U> void f(T, U);
  };

When we instantiate X<int>, we now instantiate the declaration
X<int>::f, which looks like this:

  template<typename U> void X<int>::f(int, U);

The path this takes through
TemplateDeclInstantiator::VisitCXXMethodDecl is convoluted and
ugly, but I don't know how to improve it yet. I'm resting my hopes on
the multi-level substitution required to instantiate definitions of
nested templates, which may simplify this code as well.

More testing to come...

llvm-svn: 80252

scalar_to_vector is fully legal now

llvm-svn: 80251

llvm-svn: 80250

llvm-svn: 80249

Add a OverloadResolutionFlags and start converting some of the overload methods over to using it instead of bools arguments.

llvm-svn: 80248

llvm-svn: 80247

Add a testcase.

llvm-svn: 80246

No idea whether this is profitable or not.

llvm-svn: 80245

See http://llvm.org/PR4687 for more info and links.

llvm-svn: 80244

llvm-svn: 80240

llvm-svn: 80239

llvm-svn: 80237

llvm-svn: 80236

 - No relocations yet, of course.

llvm-svn: 80235

 - Note, this is a gigantic hack, with the sole purpose of unblocking further
   work on the assembler (its also possible to test the mathcer more completely
   now).

 - Despite being a hack, its actually good enough to work over all of 403.gcc
   (although some encodings are probably incorrect). This is a testament to the 
   beauty of X86's MachineInstr, no doubt! ;)

llvm-svn: 80234

printer.

llvm-svn: 80233

llvm-svn: 80232

llvm-svn: 80231

llvm-svn: 80230

llvm-svn: 80229

llvm-svn: 80228

llvm-svn: 80227

llvm-svn: 80226

llvm-svn: 80225

Clean up the minor mess I caused with removing iterator.h. I shall take care of 80-col violations and the FIXME later. (Thanks goodness that I live in another continent, so the monkeypox did not strike me :-)

llvm-svn: 80224

calls into a function and if the calls bring in arrays, try to merge
them together to reduce stack size.  For example, in the testcase
we'd previously end up with 4 allocas, now we end up with 2 allocas.

As described in the comments, this is not really the ideal solution
to this problem, but it is surprisingly effective.  For example, on
176.gcc, we end up eliminating 67 arrays at "gccas" time and another
24 at "llvm-ld" time.

One piece of concern that I didn't look into: at -O0 -g with
forced inlining this will almost certainly result in worse debug
info.  I think this is acceptable though given that this is a case
of "debugging optimized code", and we don't want debug info to
prevent the optimizer from doing things anyway.

llvm-svn: 80215

llvm-svn: 80214

llvm-svn: 80213

When checking whether one declaration context encloses another, make sure to look at the primary contexts. Thanks to Eli for the test case

llvm-svn: 80212

llvm-svn: 80211

llvm-svn: 80210

llvm-svn: 80209

llvm-svn: 80208