which is: { <4 x float>, <4 x float> } should continue to go through memory.

llvm-svn: 134946

people write useful cleanup classes.

llvm-svn: 134942

specified, 128 avx code is used and we're not sure yet if this the behavior
we want (and if it does, some improvements are needed before relying on it).

llvm-svn: 134939

Patch by Caitlin Sadowski.

llvm-svn: 134938

into a static helper.

Original patch by Caitlin Sadowski, style tweaks by me.

llvm-svn: 134937

llvm-svn: 134935

add one more testcase.

llvm-svn: 134934

llvm-svn: 134932

Revert r134898, "test/Frontend/dependency-gen.c: Mark XFAIL: mingw due to PR10331. to appease mingw-target (and non-mingw-host) builds.

PR10331 is still alive I suppose.

llvm-svn: 134931

llvm-svn: 134928

llvm-svn: 134927

llvm-svn: 134926

llvm-svn: 134925

llvm-svn: 134919

llvm-svn: 134918

llvm-svn: 134916

llvm-svn: 134913

require destruction and there is possibility of that without
construction. Thanks Johnm for review and suggestions offline.
// rdar://9535237.

llvm-svn: 134906

When two different types has the same text representation in the same
diagnostic message, print an a.k.a. after the type if the a.k.a. gives extra
information about the type.

class versa_string;

typedef versa_string string;

namespace std {template <typename T> class vector;}

using std::vector;

void f(vector<string> v);

namespace std {
class basic_string;
typedef basic_string string;
template <typename T> class vector {};
void g() {
  vector<string> v;
  f(v);
}
}

Old message:
----------------
test.cc:15:3: error: no matching function for call to 'f'
  f(&v);
  ^
test.cc:7:6: note: candidate function not viable: no known conversion from
      'vector<string>' to 'vector<string>' for 1st argument
void f(vector<string> v);
     ^
1 error generated.

New message:
---------------
test.cc:15:3: error: no matching function for call to 'f'
  f(v);
  ^
test.cc:7:6: note: candidate function not viable: no known conversion from
      'vector<string>' (aka 'std::vector<std::basic_string>') to
      'vector<string>' (aka 'std::vector<versa_string>') for 1st argument
void f(vector<string> v);
     ^
1 error generated.

llvm-svn: 134904

llvm-svn: 134899

llvm-svn: 134898

functions. Fixes <rdar://problem/9731999>.

llvm-svn: 134897

llvm-svn: 134896

llvm-svn: 134893

llvm-svn: 134892

llvm-svn: 134891

 - an off-by-one error in emission of irregular array limits for
   InitListExprs
 - use an EH partial-destruction cleanup within the normal
   array-destruction cleanup
 - get the branch destinations right for the empty check
Also some refactoring which unfortunately obscures these changes.

llvm-svn: 134890

llvm-svn: 134888

llvm-svn: 134885

llvm-svn: 134880

Solution is to set output stdout to binary mode to prevent newline conversion (\n => \r\n).

llvm-svn: 134879

llvm-svn: 134877

llvm-svn: 134876

llvm-svn: 134875

llvm-svn: 134874

llvm-svn: 134873

tools/c-arcmt-test/Makefile: Add clangARCMigrate.a clangRewrite.a to USEDLIBS to satisfy linking on cygming.

FIXME: tools/c-*.exe should be linked to clang.dll on cygming. llvm/Makefile.rules is not aware of bin/clang.dll.
llvm-svn: 134871

llvm-svn: 134870

llvm-svn: 134869

is called whenever a tag type is completed.  We previously used that
as the sign to layout the codegen representation for the tag type,
which worked but meant that we laid out *every* completed type, whether
it was used or not.

Now we just lay out the type if we've already seen it somehow else.
This means that we lay out types we've used but haven't seen a body
for, but we don't lay out tons of stuff that noone cares about.

llvm-svn: 134866