From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (unknown [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id 9A14CDF965 for ; Fri, 22 Aug 2008 07:05:03 +1000 (EST) Date: Thu, 21 Aug 2008 14:05:02 -0700 (PDT) Message-Id: <20080821.140502.146697690.davem@davemloft.net> To: galak@kernel.crashing.org Subject: Re: [PATCH] math-emu: Add support for reporting exact invalid exception From: David Miller In-Reply-To: <1219323021-7273-2-git-send-email-galak@kernel.crashing.org> References: <1219323021-7273-1-git-send-email-galak@kernel.crashing.org> <1219323021-7273-2-git-send-email-galak@kernel.crashing.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Kumar Gala Date: Thu, 21 Aug 2008 07:50:21 -0500 > Some architectures (like powerpc) provide status information on the exact > type of invalid exception. This is pretty straight forward as we already > report invalid exceptions via FP_SET_EXCEPTION. > > We add new flags (FP_EX_INVALID_*) the architecture code can define if it > wants the exact invalid exception reported. > > We had to split out the INF/INF and 0/0 cases for divide to allow reporting > the two invalid forms properly. > > Signed-off-by: Kumar Gala Acked-by: David S. Miller