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~
