diff options
author | Michael Gottesman <mgottesman@apple.com> | 2013-06-24 09:57:59 +0000 |
---|---|---|
committer | Michael Gottesman <mgottesman@apple.com> | 2013-06-24 09:57:59 +0000 |
commit | fb25071a18ef24949f2f422c919b85340d6c6e2a (patch) | |
tree | c862547e5631719a0c548b8a51e77460be417823 /lib/Support/APFloat.cpp | |
parent | c29f5dc29eff6f00e23eb24a6be2b27a558aee98 (diff) | |
download | llvm-fb25071a18ef24949f2f422c919b85340d6c6e2a.tar.gz llvm-fb25071a18ef24949f2f422c919b85340d6c6e2a.tar.bz2 llvm-fb25071a18ef24949f2f422c919b85340d6c6e2a.tar.xz |
[APFloat] Removed a assert from significandParts() which says that one can only access the significand of FiniteNonZero/NaN floats.
The method significandParts() is a helper method meant to ease access to
APFloat's significand by allowing the user to not need to be aware of whether or
not the APFloat is using memory allocated in the instance itself or in an
external array.
This assert says that one can only access the significand of FiniteNonZero/NaN
floats. This makes it cumbersome and more importantly dangerous when one wishes
to zero out the significand of a zero/infinity value since one will have to deal
with the aforementioned quandary related to how the memory in APFloat is
allocated.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@184711 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Support/APFloat.cpp')
-rw-r--r-- | lib/Support/APFloat.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/lib/Support/APFloat.cpp b/lib/Support/APFloat.cpp index ff8b7f157e..db1d61c281 100644 --- a/lib/Support/APFloat.cpp +++ b/lib/Support/APFloat.cpp @@ -847,8 +847,6 @@ APFloat::significandParts() const integerPart * APFloat::significandParts() { - assert(category == fcNormal || category == fcNaN); - if (partCount() > 1) return significand.parts; else |