This makes it more clear that the symbol is an internal, compiler-generated
name and gives a little more description about its contents.

llvm-svn: 119564

It was mistakenly looking at the pointer type when checking for the size of
global variables.  This is a partial fix for Radar 8673120.

llvm-svn: 119563

functions of ScalarEvolution, in preparation for memoization and
other optimizations.

llvm-svn: 119562

llvm-svn: 119560

in the MC lowering process.

llvm-svn: 119559

Avoid isel movcc of large immediates when the large immediate is available in a register. These immediates aren't free.

llvm-svn: 119558

to avoid an unneeded dependence.

llvm-svn: 119557

needs to be checked that this won't break LCSSA form.
Change the existing checking method to a more direct one:
rather than seeing if all predecessors belong to the loop,
check that the replacing value is either not in any loop or
is in a loop that contains the phi node.

llvm-svn: 119556

llvm-svn: 119555

instead of in SCEVAddRecExpr's constructor, in preparation for an
upcoming change.

llvm-svn: 119554

llvm-svn: 119553

results in the gdb testsuite.

llvm-svn: 119552

llvm-svn: 119551

default ctor with ConstantRange.

llvm-svn: 119550

Add a ThreadPlanAssemblyTracer that takes just a thread (since that's how we call it from ThreadPlanBase...)

llvm-svn: 119549

and xor. The 32-bit move immediates can be hoisted out of loops by machine
LICM but the isel hacks were preventing them.

Instead, let peephole optimization pass recognize registers that are defined by
immediates and the ARM target hook will fold the immediates in.

Other changes include 1) do not fold and / xor into cmp to isel TST / TEQ
instructions if there are multiple uses. This happens when the 'and' is live
out, machine sink would have sinked the computation and that ends up pessimizing
code. The peephole pass would recognize situations where the 'and' can be
toggled to define CPSR and eliminate the comparison anyway.

2) Move peephole pass to after machine LICM, sink, and CSE to avoid blocking
important optimizations.

rdar://8663787, rdar://8241368

llvm-svn: 119548

llvm-svn: 119547

llvm-svn: 119546

llvm-svn: 119545

llvm-svn: 119544

nonofragile-abi2. Fixes //rdar://8673791

llvm-svn: 119543

llvm-svn: 119542

llvm-svn: 119541

llvm-svn: 119540

llvm-svn: 119539

llvm-svn: 119538

llvm-svn: 119537

instructions out of InstCombine and into InstructionSimplify.  While
there, introduce an m_AllOnes pattern to simplify matching with integers
and vectors with all bits equal to one.

llvm-svn: 119536

assert(a || b && "bad");

since this is safe. This way we avoid a big source of such warnings which in this case are practically useless.

Note that we don't handle *all* cases where precedence wouldn't matter because of constants since
this is a bit costly to check, and IMO clarifying precedence with parentheses is good for
readability in general.

llvm-svn: 119533

Put warn_logical_and_in_logical_or warning in new warning group "logical-op-parentheses" member of "parentheses".

llvm-svn: 119532

llvm-svn: 119529

llvm-svn: 119522

llvm-svn: 119518

on a non-type declaration, as GCC permits it on variables too.
This fixes PR8635.

llvm-svn: 119517

an implicit "this"; it causes clang_getCursor() to find the implicit
"this" expression (which isn't written in the source!) rather than the
actual member.

llvm-svn: 119516

llvm-svn: 119515

interest (e.g., as used by clang_getCursor()), count the
decl-specifier-seq as part of the source range, as we do for
clang_annotateTokens(). Makes clang_getCursor() work properly for the
result types of functions, for example.

llvm-svn: 119514

llvm-svn: 119512

Fixes PR8631.

llvm-svn: 119511

 - No immediate use, but maybe someone feels like hacking on it.

llvm-svn: 119510