The MOV64ri64i32 instruction required hacky MCInst lowering because it
was allocated as setting a GR64, but the eventual instruction ("movl")
only set a GR32. This converts it into a so-called "MOV32ri64" which
still accepts a (appropriate) 64-bit immediate but defines a GR32.
This is then converted to the full GR64 by a SUBREG_TO_REG operation,
thus keeping everyone happy.

This fixes a typo in the opcode field of the original patch, which
should make the legact JIT work again (& adds test for that problem).

llvm-svn: 183068

llvm-svn: 183067

Removed a comment above an include which is unnecessary and added a missing closing @} for a doxygen comment.

llvm-svn: 183065

llvm-svn: 183064

Also added a few more method comments and performed some copy editing.

llvm-svn: 183063

Jordan has pointed out that it is valuable to warn in cases when the arguments to init escape.
For example, NSData initWithBytes id not going to free the memory.

llvm-svn: 183062

This also makes TableGen able to compute sizes/offsets of synthesized
indices representing tuples.

llvm-svn: 183061

Fixes rdar:14036816, PR16130.

There is an opportunity to compute precise trip counts for 'or'
expressions and multi-exit loops.
rdar:14038809: Optimize trip count computation for multi-exit loops.

To do this we need to record the fact that ExitLimit assumes NSW. When
it does not we can safely assume that the loop trip count is the
minimum ExitLimt across all subexpressions and loop exits.

llvm-svn: 183060

seems to have caused PR16192 and other JIT related failures.

llvm-svn: 183059

llvm-svn: 183058

llvm-svn: 183057

llvm-svn: 183056

llvm-svn: 183055

llvm-svn: 183054

llvm-svn: 183053

llvm-svn: 183052

llvm-svn: 183051

llvm-svn: 183050

All running threads will be detected and stopped on attach and all threads get resumed on detach.

llvm-svn: 183049

'ivar' was used inside a record/union used 
as argument to __typeof. // rdar14037151 pr5984

llvm-svn: 183048

Use ScalarEvolution's getBackedgeTakenCount API instead of getExitCount since
that is really what we want to know. Using the more specific getExitCount was
safe because we made sure that there is only one exiting block.

No functionality change.

llvm-svn: 183047

llvm-svn: 183046

Account for the cost of scaling factor in Loop Strength Reduce when rating the
formulae. This uses a target hook.

The default implementation of the hook is: if the addressing mode is legal, the
scaling factor is free.

<rdar://problem/13806271>

llvm-svn: 183045

- should resolve remaining buildbot issues with debian/clang builder

llvm-svn: 183044

llvm-svn: 183043

llvm-svn: 183042

llvm-svn: 183041

llvm-svn: 183040

- as per review comment from Dimitry Andric!

llvm-svn: 183039

Patch by Ed Maste!

llvm-svn: 183038

Add 'JoinExistingSession' to XPC for root debugging.

llvm-svn: 183037

I renamed the function at one point in time, but forgot to fix the
layout of the arguments.

llvm-svn: 183036

We check that instructions in the loop don't have outside users (except if
they are reduction values). Unfortunately, we skipped this check for
if-convertable PHIs.

Fixes PR16184.

llvm-svn: 183035

llvm-svn: 183034

For integer types of sizes 1, 2, 4 and 8, libcompiler-rt (and libgcc)
provide atomic functions that pass parameters by value and return
results directly.

libgcc and libcompiler-rt only provide optimized libcalls for
__atomic_fetch_*, as generic libcalls on non-integer types would make
little sense. This means that we can finally make __atomic_fetch_* work
on architectures for which we don't provide these operations as builtins
(e.g. ARM).

This should fix the dreaded "cannot compile this atomic library call
yet" error that would pop up once every while.

llvm-svn: 183033

- missing #include <cstdlib> in Mangled.cpp
- missing include dirs in FreeBSD CMakeLists.txt

Patch by Ed Maste!

llvm-svn: 183032

Fixes a leak found by valgrind.

llvm-svn: 183031

Fixing an issue where formats would not propagate from parents to children in all cases
Details follow:
an SBValue has children and those are fetched along with their values
Now, one calls SBValue::SetFormat() on the parent
Technically, the format choices should propagate onto the children (see ValueObject::GetFormat())
But if the children values are already fetched, they won't notice the format change and won't update themselves
This commit fixes that by making ValueObject::GetValueAsCString() check if any format change intervened from the previous call to the current one
A test case is also added

llvm-svn: 183030

Also add the "=" to the matched pattern, to see whether we actually save
the loaded value.

llvm-svn: 183029

llvm-svn: 183028