them, but hopefully we won't. And this is not the right data structure
to do it anyway.

llvm-svn: 117412

llvm-svn: 117411

of static data member of a class template.
Fixes //rdar :// 8562966 and pr8409.

llvm-svn: 117410

explicit about the operands. Split out the different variants into separate
instructions. This gives us the ability to, among other things, assign
different scheduling itineraries to the variants. rdar://8477752.

llvm-svn: 117409

the remainder register.

Example:

bb0:
  x = 1
bb1:
  use(x)
  ...
  x = 2
  jump bb1

When x is isolated in bb1, the inner part breaks into two components, x1 and x2:

bb0:
  x0 = 1
bb1:
  x1 = x0
  use(x1)
  ...
  x2 = 2
  x0 = x2
  jump bb1

llvm-svn: 117408

components, each should get its own virtual register.

llvm-svn: 117407

necessary to get correct hasPHIKill flags.

llvm-svn: 117406

llvm-svn: 117405

llvm-svn: 117404

in IR gen, and use those to fix a correctness issue with bool atomic
intrinsics.  rdar://problem/8461234

llvm-svn: 117403

llvm-svn: 117402

llvm-svn: 117401

llvm-svn: 117400

llvm-svn: 117399

llvm-svn: 117398

different ways. Check once, and use an assert to handle
consistency checking.

llvm-svn: 117397

llvm-svn: 117396

llvm-svn: 117395

llvm-svn: 117394

doesn't need its return value.

llvm-svn: 117393

SlotIndexes when available.

llvm-svn: 117392

llvm-svn: 117391

llvm-svn: 117390

llvm-svn: 117389

llvm-svn: 117388

llvm-svn: 117387

so that it's done in one place.

llvm-svn: 117386

llvm-svn: 117385

llvm-svn: 117384

causing modules that haven't already been parsed from being searched.

llvm-svn: 117383

llvm-svn: 117382

llvm-svn: 117381

llvm-svn: 117380

llvm-svn: 117378

llvm-svn: 117377

s/endScope/endInstruction/g

llvm-svn: 117376

llvm-svn: 117374

llvm-svn: 117373

typo. This can happen with context-sensitive keywords like "super",
when typo correction didn't know that "super" wasn't permitted in this
context.

llvm-svn: 117372

Magic is happening that we don't understand.

llvm-svn: 117370