Introduce needsCleanup() for APFloat and APInt.

This is needed in clang so one can check if the object needs the
destructor called after its memory was freed. This is useful when
creating many APInt/APFloat objects with placement new, where the
overhead of tracking the pointers for cleanup is significant.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@183100 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Manuel Klimek 2013-06-03 13:03:05 +00:00
parent e7cbb792c9
commit abff3aa821
3 changed files with 8 additions and 2 deletions

View File

@ -201,6 +201,9 @@ public:
/// @}
/// \brief Returns whether this instance allocated memory.
bool needsCleanup() const { return partCount() > 1; }
/// \name Convenience "constructors"
/// @{

View File

@ -293,7 +293,7 @@ public:
/// \brief Destructor.
~APInt() {
if (!isSingleWord())
if (needsCleanup())
delete[] pVal;
}
@ -303,6 +303,9 @@ public:
/// method Read).
explicit APInt() : BitWidth(1) {}
/// \brief Returns whether this instance allocated memory.
bool needsCleanup() const { return !isSingleWord(); }
/// Used to insert APInt objects, or objects that contain APInt objects, into
/// FoldingSets.
void Profile(FoldingSetNodeID &id) const;

View File

@ -580,7 +580,7 @@ APFloat::initialize(const fltSemantics *ourSemantics)
void
APFloat::freeSignificand()
{
if (partCount() > 1)
if (needsCleanup())
delete [] significand.parts;
}