based on a modifier, split it into two functions.

llvm-svn: 134637

llvm-svn: 134636

numbers should be printed instead of symbolic register names in
MCAsmStreamer::EmitRegisterName. This is necessary because some versions of
GNU assembler won't accept code in which symbolic register names are used in
cfi directives. There is no change in behavior unless the flag is explicitly
set to true by a backend.

llvm-svn: 134635

function. Fixes PR10233!

llvm-svn: 134634

llvm-svn: 134633

llvm-svn: 134632

client code.

My bad.

llvm-svn: 134631

llvm-svn: 134630

llvm-svn: 134629

llvm-svn: 134628

llvm-svn: 134627

llvm-svn: 134626

before the offset. This change will enable simplification of function
MipsRegisterInfo::eliminateFrameIndex.

llvm-svn: 134625

object to a __weak object/type. // rdar://9732636.
This is objc side of things. objc++ side tbd.

llvm-svn: 134624

llvm-svn: 134623

llvm-svn: 134622

llvm-svn: 134621

If known DebugLocs do not match then two DBG_VALUE machine instructions are not identical. For example,

        DBG_VALUE 3.310000e+02, 0, !"ds"; dbg:sse.stepfft.c:138:18 @[ sse.stepfft.c:32:10 ]
        DBG_VALUE 3.310000e+02, 0, !"ds"; dbg:sse.stepfft.c:138:18 @[ sse.stepfft.c:31:10 ]

These two MIs represent identical value, 3.31...,  for one variable, ds, but they are not identical because the represent two separate instances of inlined variable "ds". 

llvm-svn: 134620

llvm-svn: 134619

fault if no arguments are given.

llvm-svn: 134618

llvm-svn: 134617

llvm-svn: 134616

clang_codeCompleteGetContexts(), that provides the client with
information about the context in which code completion has occurred
and what kinds of entities make sense as completions at that
point. Patch by Connor Wakamo!

llvm-svn: 134615

llvm-svn: 134614

llvm-svn: 134613

If we're using the pure non-fragile ABI, then skip some of the contortions required to support the transitional ABI.

llvm-svn: 134612

Set a flag to tell the runtime when we're compiling in ARC mode and use the pure-nonfragile ABI for both ARC and GC mode.

llvm-svn: 134611

Fix example: variable is initialized to 10 and then has 11 stored in it, but in the expanded version is initialized to 11.

llvm-svn: 134610

multiply-accumulate instructions with separate rounding steps.

llvm-svn: 134609

llvm-svn: 134608

llvm-svn: 134607

llvm-svn: 134606

where we have an immediate need of a retained value.

As an exception, don't do this when the call is made as the immediate
operand of a __bridge retain.  This is more in the way of a workaround
than an actual guarantee, so it's acceptable to be brittle here.

rdar://problem/9504800

llvm-svn: 134605

llvm-svn: 134601

llvm-svn: 134599

constructing itself and causing unexpected things to happen
in LLDB.

llvm-svn: 134598

llvm-svn: 134595

group class: OptionGroupVariable. It gets initialized with
a boolean that indicates if the frame specific options are
included so that this can be used in both the "frame variable"
and "target variable" commands.

Removed the global functionality from the "frame variable" 
command. Users should switch to using the "target variable"
command.

llvm-svn: 134594

hasPredecessorHelper function allows predecessors to be cached to speed up
repeated invocations. This fixes PR10186.

X.isPredecessorOf(Y) now just calls Y.hasPredecessor(X)

Y.hasPredecessor(X) calls Y.hasPredecessorHelper(X, Visited, Worklist) with
empty Visited and Worklist sets (i.e. no caching over invocations).

Y.hasPredecessorHelper(X, Visited, Worklist) caches search state in Visited
and Worklist to speed up repeated calls. The Visited set is searched for X
before going to the worklist to further search the DAG if necessary.

llvm-svn: 134592

llvm-svn: 134591