Add a bit IsUndef to MachineOperand. This indicates the def / use register operand is defined by an implicit_def. That means it can def / use any register and passes (e.g. register scavenger) can feel free to ignore them.

The register allocator, when it allocates a register to a virtual register defined by an implicit_def, can allocate any physical register without worrying about overlapping live ranges. It should mark all of operands of the said virtual register so later passes will do the right thing.

This is not the best solution. But it should be a lot less fragile to having the scavenger try to track what is defined by implicit_def.

llvm-svn: 74518

llvm-svn: 74517

create TypedViewRegion for it.

llvm-svn: 74516

llvm-svn: 74515

llvm-svn: 74514

David Majnemer!

llvm-svn: 74513

llvm-svn: 74512

llvm-svn: 74511

llvm-svn: 74510

llvm-svn: 74509

llvm-svn: 74508

llvm-svn: 74507

Remove ASTContext parameter from DeclContext's methods. This change cascaded down to other Decl's methods and changes to call sites started "escalating".
Timings using pre-tokenized "cocoa.h" showed only a ~1% increase in time run between and after this commit.

llvm-svn: 74506

It's not getASTContext() to avoid "getASTContext is ambiguous" compiler errors for subclasses of both Decl and DeclContext.

llvm-svn: 74505

Timings showed no significant difference before and after the commit.

llvm-svn: 74504

llvm-svn: 74503

llvm-svn: 74502

The implementations of these methods can Use Decl::getASTContext() to get the ASTContext.

This commit touches a lot of files since call sites for these methods are everywhere.
I used pre-tokenized "carbon.h" and "cocoa.h" headers to do some timings, and there was no real time difference between before the commit and after it.

llvm-svn: 74501

llvm-svn: 74500

llvm-svn: 74499

llvm-svn: 74498

legally negate an MCValue.

llvm-svn: 74497

llvm-svn: 74496

llvm-svn: 74495

This will allow it to be used in unittests that use gtest's
EXPECT_EQ.

llvm-svn: 74494

This is simple enough, but then I thought it would be nice to make PrintingPolicy
get a LangOptions so that various things can key off "bool" and "C++" independently.
This spiraled out of control.  There are many fixme's, but I think things are slightly
better than they were before.

One thing that can be improved: CFG should probably have an ASTContext pointer in it,
which would simplify its clients.

llvm-svn: 74493

llvm-svn: 74492

llvm-svn: 74491

llvm-svn: 74490

 - Don't print "Parsing" in front of every message.

 - Take additional "type" argument which is prepended to the message (with ": ")
   if given.

 - Update clients to print errors (warnings) as:
<filename>:<line number>: error(warning): ...

llvm-svn: 74489

Add LLVMContext, which will eventually be used as a container for privatizing a lot of (currently) global state, including the
constant and type uniquing tables.  For now, just make it a wrapper around the existing APIs.

llvm-svn: 74488

llvm-svn: 74487

llvm-svn: 74486

llvm-svn: 74485

llvm-svn: 74484

llvm-svn: 74483

llvm-svn: 74482

llvm-svn: 74481

list.

llvm-svn: 74480

llvm-svn: 74479