From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57771) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZRmx-00024D-L5 for qemu-devel@nongnu.org; Thu, 24 Oct 2013 16:45:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZRmo-0002Fq-U3 for qemu-devel@nongnu.org; Thu, 24 Oct 2013 16:45:51 -0400 Sender: Richard Henderson Message-ID: <526986CF.8090503@twiddle.net> Date: Thu, 24 Oct 2013 13:45:03 -0700 From: Richard Henderson MIME-Version: 1.0 References: <526947CA.4020504@gmail.com> <52694A24.3050509@gmail.com> In-Reply-To: <52694A24.3050509@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 15/19] Add VSX xmax/xmin Instructions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tom Musta , QEMU Developers Cc: "qemu-ppc@nongnu.org" On 10/24/2013 09:26 AM, Tom Musta wrote: > Because of the Power ISA definitions of maximum and minimum > on various boundary cases, the standard softfloat comparison > routines (e.g. float64_lt) do not work as well as one might > think. Therefore specific routines for comparing 64 and 32 > bit floating point numbers are implemented in the PowerPC > helper code. Really? All I see in the document is ">fp", used both here in the minmax insn and in the cmp insn. If the softfloat compare isn't good enough for minmax, how can it be good enough for cmp? r~