walking the asm arguments once and stashing their Values.  This is
wrong because the same memory location can be in the list twice, and
if the first one has a sunkaddr substituted, the stashed value for the
second one will be wrong (use-after-free).  PR 8154.

llvm-svn: 114104

It is possible, under specific circumstances involving ptrtoint ConstantExpr's, for LVI to end up trying to merge
a Constant into a ConstantRange.  Handle this conservatively for now, rather than asserting.  The testcase is
more complex that I would like, but the manifestation of the problem is sensitive to iteration orders and the state of the
LVI cache, and I have not been able to reproduce it with manually constructed or simplified cases.

Fixes PR8162.

llvm-svn: 114103

checks that the launched process writes its standard output there.

llvm-svn: 114102

llvm-svn: 114101

llvm-svn: 114100

llvm-svn: 114099

(PICLDRB, et. al.) and PICSTR*

llvm-svn: 114098

to replace an instruction with itself.  Add a predicate to the simplifier to prevent this case.

llvm-svn: 114097

from the APFloat.

llvm-svn: 114096

llvm-svn: 114095

build tree relative search path in order to locate the lldb.py module.  When
'-i' is present, the test driver relies on the PYTHONPATH environment variable
to locate the lldb.py module.

llvm-svn: 114094

warning to handle multiple enumerators with one warning.

llvm-svn: 114093

"b" is now aliased to "regexp-break"
"p" is now aliased to "frame variable"
"print" is now aliased to "frame variable"

llvm-svn: 114092

llvm-svn: 114091

llvm-svn: 114087

llvm-svn: 114086

llvm-svn: 114085

Make this method static. Bad things(tm) happen when a non-static method is called in a constructor's initializer list.

llvm-svn: 114084

Unbreak build, you can't take a pointer from a "register" variable. Most compilers ignore this keyword anyways.

Also remove a typedef that typedefs nothing.

llvm-svn: 114083

doesn't add any value. Instead, we'll just take the first method with
that selector that we find and create a completion for it.

llvm-svn: 114082

llvm-svn: 114081

sure to visit the protocols of protocols.

llvm-svn: 114079

missing the opening bracket '[', e.g.,

  NSArray <CC>

at function scope. Previously, we would only give trivial completions
(const, volatile, etc.), because we're in a "declaration name"
scope. Now, we also provide completions for class methods of NSArray,
e.g.,

  alloc

Note that we already had support for this after the first argument,
e.g.,

  NSArray method:x <CC>

would get code completion for class methods of NSArray whose selector
starts with "method:". This was already present because we recover
as if NSArray method:x were a class message send missing the opening
bracket (which was committed in r114057).

llvm-svn: 114078

llvm-svn: 114077

llvm-svn: 114075

This cleans up after the mess r108567 left in the CellSPU backend.
ORCvt-instruction were used to reinterpret registers, and the ORs were then
removed by isMoveInstr(). This patch now removes 350 instrucions of format:
	or $3, $3, $3
(from the 52 testcases in CodeGen/CellSPU). One case of a nonexistant or is
checked for.

Some moves of the form 'ori $., $., 0' and 'ai $., $., 0' still remain.

llvm-svn: 114074

Cameron Esfahani, tweaked to use array_lengthof.

llvm-svn: 114073

with attribute warn_unused_result" here - suppress the warning harder.

llvm-svn: 114072

derive from temporaries of the same type.  Black-list member expressions
as well.

llvm-svn: 114071

translation units that don't catch ObjC types.  rdar://problem/8434851

llvm-svn: 114070

llvm-svn: 114068

used for anything.

llvm-svn: 114067

instead of using default predicates on the expanded instructions.

llvm-svn: 114066

Refactored BugReporter to refer to EndNode as ErrorNode. We currently make the assumption that EndNode == ErrorNode, but upcoming changes will break this.

llvm-svn: 114065

unnecessary dtor for MCOperand.

llvm-svn: 114064

llvm-svn: 114062

llvm-svn: 114061

Prospective fix for broken commit in r114045.

llvm-svn: 114060

llvm-svn: 114059

This will remove the confusion experienced when previous test runs left some
files (both intermediate or by-product as a result of the test).

lldbtest.TestBase defines a classmethod tearDownClass(cls) which invokes the
platform-specific cleanup() function as defined by the plugin; after that, it
invokes a subclass-specific function classCleanup(cls) if defined; and, finally,
it restores the old working directory.

An example of classCleanup(cls) is in settings/TestSettings.py:

    @classmethod
    def classCleanup(cls):
        system(["/bin/sh", "-c", "rm output.txt"])

where it deletes the by-product "output.txt" as a result of running a.out.

llvm-svn: 114058