new gcc warning that complains on self-assignments and
self-initializations.

llvm-svn: 122458

llvm-svn: 112708

llvm-svn: 85254

same Value without breaking things.

llvm-svn: 83861

llvm-svn: 78948

http://llvm.org/viewvc/llvm-project?view=rev&revision=78127, I'm changing the
ExecutionEngine's global mappings to hold AssertingVH<const GlobalValue>. That
way, if unregistering a mapping fails to actually unregister it, we'll get an
assert. Running the jit nightly tests didn't uncover any actual instances of
the problem.

This also uncovered the fact that AssertingVH<const X> didn't work, so I fixed
that too.

llvm-svn: 78400

llvm-svn: 77730

metadata related, which I'm waiting on to avoid conflicting with Devang.

llvm-svn: 77721

Revert the ConstantInt constructors back to their 2.5 forms where possible, thanks to contexts-on-types.  More to come.

llvm-svn: 77011

llvm-svn: 75703

Begin the painful process of tearing apart the rat'ss nest that is Constants.cpp and ConstantFold.cpp.
This involves temporarily hard wiring some parts to use the global context.  This isn't ideal, but it's
the only way I could figure out to make this process vaguely incremental.

llvm-svn: 75445

llvm-svn: 71993

to make the copy constructor and destructor protected, and corresponding
adjustments to the unittests.

llvm-svn: 70644

the comparison operators were not only unnecessary in the presence of the
implicit conversion; they caused ambiguous overload errors. So I deleted them.

llvm-svn: 70243