llvm-svn: 147820

source file. Otherwise -g -save-temps will error out on the compile
of any .c file.

Fixes about 4000 of the errors in the clang-tests gdb test suite.

llvm-svn: 147819

llvm-svn: 147818

c++ objects with non-trivial assignment/copy functions.
Also, one additional sema check. // rdar://6137845

llvm-svn: 147817

functions that can create file descriptors and close them. It will warn when
there close file descriptor call that returns with EBADF and show the 
corresponding stack backtraces that caused the issue. It will also log all
file descriptor create and delete calls. See the comments at the top of
FDInterposing.cpp for all of the details.

llvm-svn: 147816

in the module when dumping the information in addition to all info that we
were previously showing.

llvm-svn: 147815

the linker driver is found.

llvm-svn: 147814

takes to open and index BSD archives.

llvm-svn: 147813

llvm-svn: 147812

llvm-svn: 147811

[asan] temporary reinstate string.h/strings.h. Removal of those caused a Mac build failulre which I failed to observe before the commit

llvm-svn: 147810

llvm-svn: 147809

intended to cover C++ class definitions.

llvm-svn: 147808

llvm-svn: 147807

The pass is prone to looping, and it is better to crash than loop
forever, even in a -Asserts build.

<rdar://problem/10660175>

llvm-svn: 147806

llvm-svn: 147805

llvm-svn: 147802

After collecting chains, check if any should be materialized. If so,
hide the chained IV users from the LSR solver. LSR will only solve for
the head of the chain. GenerateIVChains will then materialize the
chained IV users by computing the IV relative to its previous value in
the chain.

In theory, chained IV users could be exposed to LSR's solver. This
would be considerably complicated to implement and I'm not aware of a
case where we need it. In practice it's more important to
intelligently prune the search space of nontrivial loops before
running the solver, otherwise the solver is often forced to prune the
most optimal solutions. Hiding the chained users does this well, so
that LSR is more likely to find the best IV for the chain as a whole.

llvm-svn: 147801

llvm-svn: 147799

llvm-svn: 147798

This collects a set of IV uses within the loop whose values can be
computed relative to each other in a sequence. Following checkins will
make use of this information.

llvm-svn: 147797

llvm-svn: 147796

llvm-svn: 147794

llvm-svn: 147793

llvm-svn: 147792

llvm-svn: 147791

it was checked in as:
 virtual bool ABI::FixCodeAddress (lldb::addr_t pc);

when it should have been:

virtual lldb::addr_t ABI::FixCodeAddress (lldb::addr_t pc);


 

llvm-svn: 147790

llvm-svn: 147789

llvm-svn: 147788

AsmParser holds info specific to target parser.
AsmParserVariant holds info specific to asm variants supported by the target.

llvm-svn: 147787

padding insertion will not work if the coerced type is not a structure.

llvm-svn: 147786

llvm-svn: 147785

llvm-svn: 147784

Thanks to David Blaikie for pointing this out.

llvm-svn: 147783

the anonymous namespace to its parent. Semantically, this means that
the anonymous namespaces defined in one module are distinct from the
anonymous namespaces defined in another module.

llvm-svn: 147782

Patch by  Joe Groff!

llvm-svn: 147781

that we can merge, for example, two occurrences of

  namespace N { void f(); }

in two disjoint modules.

llvm-svn: 147780

llvm-svn: 147779

modules. Teach name lookup into namespaces to search in each of the
merged DeclContexts as well as the (now-primary) DeclContext. This
supports the common case where two different modules put something
into the same namespace.

llvm-svn: 147778

This subsumes several other transforms while enabling us to catch more cases.

llvm-svn: 147777