It's similar to "linker_private_weak", but it's known that the address of the
object is not taken. For instance, functions that had an inline definition, but
the compiler decided not to inline it. Note, unlike linker_private and
linker_private_weak, linker_private_weak_def_auto may have only default
visibility.  The symbols are removed by the linker from the final linked image
(executable or dynamic library).

llvm-svn: 111684

not part of the IR, are not uniqued, and may be safely RAUW'd.
This replaces a variety of alternate mechanisms for achieving
the same effect.

llvm-svn: 111681

llvm-svn: 111676

llvm-svn: 111673

llvm-svn: 111670

llvm-svn: 111669

llvm-svn: 111665

llvm-svn: 111661

llvm-svn: 111659

llvm-svn: 111646

pending output errors are detected.

llvm-svn: 111643

outside of outs() and errs() themselves, and they don't really
need custom classes.

llvm-svn: 111642

class which is using it.

llvm-svn: 111639

llvm-svn: 111625

llvm-svn: 111619

zero-extend operations.

llvm-svn: 111614

functionality that most command-line tools need: ensuring that the
output file gets deleted if the tool is interrupted or encounters an
error.

llvm-svn: 111595

move some constraints around.

llvm-svn: 111594

llvm-svn: 111592

it involves specific floating-point types, legalize should expand an
extending load to a non-extending load followed by a separate extend operation.
For example, we currently expand SEXTLOAD to EXTLOAD+SIGN_EXTEND_INREG (and
assert that EXTLOAD should always be supported).  Now we can expand that to
LOAD+SIGN_EXTEND.  This is needed to allow vector SIGN_EXTEND and ZERO_EXTEND
to be used for NEON.

llvm-svn: 111586

llvm-svn: 111585

of the current thread. This has the unfortunate effect that assert() and abort()
will end up bypassing our crash recovery attempts. We work around this for
anything in the same linkage unit by just defining our own versions of the
assert handler and abort.

llvm-svn: 111583

llvm-svn: 111575

llvm-svn: 111574

llvm-svn: 111571

When a set of bitmask operations, typically from a bitfield initialization, only modifies the low bytes of a value,
we can narrow the store to only over-write the affected bytes.

llvm-svn: 111568

llvm-svn: 111551

llvm-svn: 111543

llvm-svn: 111540

llvm-svn: 111537

The Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01
implements parts of C++0x based on the draft standard. An old version of
the draft had a bug that makes std::pair<T1*, T2*>(something, 0) fail to
compile. This is because the template<class U, class V> pair(U&& x, V&& y)
constructor is selected, even though it later fails to implicitly convert
U and V to frist_type and second_type.

This has been fixed in n3090, but it seems that Microsoft is not going to
update msvc.

llvm-svn: 111535

llvm-svn: 111534

rdar://8277890

llvm-svn: 111533

llvm-svn: 111531

llvm-svn: 111530

llvm-svn: 111518

llvm-svn: 111517

base registers were required. This will allow for slightly better packing
of the locals when alignment padding is necessary after callee saved registers.

llvm-svn: 111508

llvm-svn: 111500

call and jumps.

llvm-svn: 111496