llvm-svn: 192555

llvm-svn: 192554

llvm-svn: 192553

It makes apparently no change it to set this bit or not but the
docs recommand to left it cleared.

llvm-svn: 192552

llvm-svn: 192551

We were using an anti-pattern of:
 - LoadLibrary
 - GetProcAddress
 - FreeLibrary

This is problematic because of several reasons:
 - We are holding on to pointers into a library we just unloaded.
 - Calling LoadLibrary results in an increase in the reference count of
   the library in question and any libraries that it depends on and
   so-on and so-forth.  This is none too quick.

Instead, use GetModuleHandleEx with GET_MODULE_HANDLE_EX_FLAG_PIN.  This
is done because because we didn't bring the reference for the library
into existence and therefor shouldn't count on it being around later.

llvm-svn: 192550

(This is triggered by current lit tests)

llvm-svn: 192549

Patch from GM to make more implicit bools explicit since we can't stop MSVC warning about this in headers and to warn is the MSVC default. No functionality change.

llvm-svn: 192548

If the edit distance between the two macros is more than 50%, DefinedMacro may not be header guard or can be header guard of another header file or it might be defining something completely different set by the build environment.

llvm-svn: 192547

llvm-svn: 192546

llvm-svn: 192545

llvm-svn: 192544

While it is mostly a user error to have the extra semicolon,
formatting it graciously will correctly format in the cases
where we do not fully understand the code (macros).

llvm-svn: 192543

* std::string::append(int, int) can be ambiguous.
* std::vector<>::data() is a C++11 feature, use ArrayRef abstraction.

llvm-svn: 192542

llvm-svn: 192541

llvm-svn: 192540

llvm-svn: 192539

llvm-svn: 192538

Before this patch we relied on the order of phi nodes when we looked for phi
nodes of the same type. This could prevent vectorization of cases where there
was a phi node of a second type in between phi nodes of some type.

This is important for vectorization of an internal graphics kernel. On the test
suite + external on x86_64 (and on a run on armv7s) it showed no impact on
either performance or compile time.

radar://15024459

llvm-svn: 192537

Contributed-by: Peter Zotov <whitequark@whitequark.org>
llvm-svn: 192536

llvm-svn: 192535

llvm-svn: 192534

llvm-svn: 192533

llvm-svn: 192532

Patch from Rami Ylimäki and Mikael Lepistö!

llvm-svn: 192531

llvm-svn: 192530

llvm-svn: 192527

llvm-svn: 192525

llvm-svn: 192524

Patch by: Jay Cornwall

Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 192523

llvm-svn: 192522

llvm-svn: 192521

they can be better handled and optimized in the Mips16 constant island code.

llvm-svn: 192520

llvm-svn: 192519

<rdar://problem/15183226>

llvm-svn: 192518

The form must be a reference form in addDIEEntry. Which reference form to
use will be decided by the callee.

No functionality change.

llvm-svn: 192517

RTDYLDMemoryManager.

llvm-svn: 192516

attribute.  Patch by chris.wailes@gmail.com; reviewed and edited by delesley.

llvm-svn: 192515

This fixes a problem from a previous check-in where a return value was omitted.

Previously the remote/stubs-remote.ll and remote/stubs-sm-pic.ll tests were reporting passes, but they should have been failing.  Those tests attempt to link against an external symbol and remote symbol resolution is not supported.  The old RemoteMemoryManager implementation resulted in local symbols being used for resolution and the child process crashed but the test didn't notice.  With this check-in remote symbol resolution fails, and so the test (correctly) fails.

llvm-svn: 192514

tests_typestate attribute.  Patch by chris.wailes@gmail.com.

llvm-svn: 192513