From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:34487)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth@twiddle.net>) id 1QAPvk-00032p-4y
	for qemu-devel@nongnu.org; Thu, 14 Apr 2011 13:02:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rth@twiddle.net>) id 1QAPvj-0005au-6g
	for qemu-devel@nongnu.org; Thu, 14 Apr 2011 13:02:08 -0400
Received: from a.mail.sonic.net ([64.142.16.245]:39025)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth@twiddle.net>) id 1QAPvi-0005aX-R8
	for qemu-devel@nongnu.org; Thu, 14 Apr 2011 13:02:07 -0400
Message-ID: <4DA72882.7080202@twiddle.net>
Date: Thu, 14 Apr 2011 10:01:54 -0700
From: Richard Henderson <rth@twiddle.net>
MIME-Version: 1.0
References: <1302645571-20500-1-git-send-email-aurelien@aurel32.net>	<1302645571-20500-9-git-send-email-aurelien@aurel32.net>	<BANLkTim8AO7VoZp9p6GDCEXww=YpS9aonA@mail.gmail.com>	<4DA5C372.5090807@twiddle.net>	<BANLkTi=Da1ov-kA5evqwZZBkmXn2F6STqw@mail.gmail.com>	<4DA70F43.90701@twiddle.net>	<BANLkTi=xrNTBgtB1Gykg0pSARoM+cdCRQA@mail.gmail.com>	<4DA7205E.1070208@twiddle.net>
	<BANLkTin=LzT2X44ux1ZgBmof-pDv_zDf-g@mail.gmail.com>
In-Reply-To: <BANLkTin=LzT2X44ux1ZgBmof-pDv_zDf-g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 08/19] target-alpha: use new
 float64_unordered() function
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <http://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>

On 04/14/2011 09:48 AM, Peter Maydell wrote:
> Or the other approach would be to do something like
> how the 'denormal-input-went-to-zero' case is handled: have
> an extra float_flag for float_flag_output_denormal, and let
> targets either (a) special-case it or (b) merge it with
> whichever of underflow or inexact they like when constructing
> the guest-visible floating point status flags. I kind of like
> that better, actually.

Either of your proposed solutions works for me.

Either allows significant freedom in the backend to decide on
how to implement the per-instruction selection.


r~