From: Michael Gottesman Date: Mon, 24 Jun 2013 09:57:59 +0000 (+0000) Subject: [APFloat] Removed a assert from significandParts() which says that one can only acces... X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=fb25071a18ef24949f2f422c919b85340d6c6e2a;p=oota-llvm.git [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 --- diff --git a/lib/Support/APFloat.cpp b/lib/Support/APFloat.cpp index ff8b7f157ee..db1d61c2813 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