If FE forgot to provide a file name (usually it uses "stdin" as name in such situation) then make one up to ensure that debug info is not malformed.

llvm-svn: 114119

Modified Makefile.rules to allow for overwriting the ARCH make variable.

llvm-svn: 114118

Revert r114097, adding back in the assertion against replacing an Instruction by itself.  Now that CorrelatedValuePropagation is
more careful not to call SimplifyInstructionsInBlock() on an unreachable block, the issue has been fixed at a higher level.  Add
a big warning to SimplifyInstructionsInBlock() to hopefully prevent this in the future.

llvm-svn: 114117

llvm-svn: 114116

them with a smaller alignment than the rest of codegen expects.

llvm-svn: 114115

reference.

llvm-svn: 114114

with a non-default-stack-ABI-alignment (of 16).
 - This fixes the ABI convenient, but breaks codegen since we now have
   underaligned arguments. Marginal improvement overall though, and will be
   fixed in next commit.

llvm-svn: 114113

Darwin. Checked vs the handiest Linux llvm-gcc I had around, someone on Linux is
welcome to investigate more.

llvm-svn: 114112

for CreateParameterDeclaration.

llvm-svn: 114111

ClangASTContext.

llvm-svn: 114110

same order as gnu as.

llvm-svn: 114109

in an initializer.

llvm-svn: 114107

llvm-svn: 114106

to optimize unreachable blocks.

llvm-svn: 114105

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