llvm-svn: 103355

with a vector input and output into a shuffle vector.  This sort of 
sequence happens when the input code stores with one type and reloads
with another type and then SROA promotes to i96 integers, which make
everyone sad.

This fixes rdar://7896024

llvm-svn: 103354

Tweaked selector generation (GNU runtime).  Removed the use of GlobalAliases in the generated bitcode.

llvm-svn: 103353

Don't destroy the data associated with an overload resolution candidate; it's ASTContext-allocated now

llvm-svn: 103350

templates and conversion function templates. 

llvm-svn: 103349

specific message that includes the template arguments, e.g.,

test/SemaTemplate/overload-candidates.cpp:27:20: note: candidate template
      ignored: substitution failure [with T = int *]
  typename T::type get_type(const T&); // expected-note{{candidate ...
                   ^

llvm-svn: 103348

llvm-svn: 103347

patch by Nathan Jeffords!

llvm-svn: 103346

failed because the explicitly-specified template arguments did not
match its template parameters, e.g.,

test/SemaTemplate/overload-candidates.cpp:18:8: note: candidate
template
      ignored: invalid explicitly-specified argument for template
      parameter 'I'
  void get(const T&);
       ^
test/SemaTemplate/overload-candidates.cpp:20:8: note: candidate
template
      ignored: invalid explicitly-specified argument for 1st template
      parameter
  void get(const T&);
       ^

llvm-svn: 103344

this issue.

llvm-svn: 103343

functionality change. 

llvm-svn: 103342

many/too few arguments, use the same diagnostic we use for arity
mismatches in non-templates (but note that it's a function template).

llvm-svn: 103341

conflicting deduced template argument values, give a more specific
reason along with those values, e.g.,

test/SemaTemplate/overload-candidates.cpp:4:10: note: candidate template
      ignored: deduced conflicting types for parameter 'T' ('int' vs. 'long')
const T& min(const T&, const T&); 
         ^

llvm-svn: 103339

llvm-svn: 103337

llvm-svn: 103335

ungracefully.

llvm-svn: 103334

stuff.

llvm-svn: 103333

llvm-svn: 103332

llvm-svn: 103331

llvm-svn: 103330

LSRUse's Regs set after all pruning is done, rather than trying
to do it on the fly, which can produce an incomplete result.

This fixes a case where heuristic pruning was stripping all
formulae from a use, which led the solver to enter an infinite
loop.

Also, add a few asserts to diagnose this kind of situation.

llvm-svn: 103328

llvm-svn: 103327

llvm-svn: 103325

mark any declarations we see inside of that type as
"referenced". Fixes PR7079.

llvm-svn: 103323

llvm-svn: 103321

A recent change to tightly verify debug info prepared by FE caught this.
This fixes unittest build.

llvm-svn: 103320

llvm-svn: 103318

llvm-svn: 103314

llvm-svn: 103312

and not the real problem itself, by dropping debug info for i128 values.
rdar://7958162.

llvm-svn: 103310

wider than 64 bits.

llvm-svn: 103309

walk an entire AST, including all of the types, declarations,
statements, and expressions, and allowing one to easily override the
behavior of the walk at any particular node kind.

llvm-svn: 103308

but whose operand isn't a float:  specifically, __real__ and __imag__.  Instead
of filtering these out, just implement them.

Fixes <rdar://problem/7958272>.

llvm-svn: 103307

llvm-svn: 103305

llvm-svn: 103304

llvm-svn: 103303

external and the item to be relocated should not have the address of the
symbol added in.

llvm-svn: 103302

Andrew Sutton!

llvm-svn: 103301

llvm-svn: 103300

getConstantFP to accept the two supported long double
target types.  This was not the original intent, but
there are other places that assume this works and it's
easy enough to do.

llvm-svn: 103299