> On Feb 15, 2006, at 11:44, John David Anglin wrote: > > I missed this "new" define and will try it. Perhaps, this should > > take account of the situation when TARGET_SOFT_FLOAT is true. For > > example, > > When emulating all software floating-point, we still don't want to > use 128-bit floats. The whole idea is that Long_Long_Float is the
Understood. My question was what should the define for WIDEST_HARDWARE_FP_SIZE be when generating code for a target with no hardware floating point support (e.g., when TARGET_SOFT_FLOAT is true)? Besides the accuracy issue, it has occured to me that the DWARF2 EH support probably can't unwind successfully from exceptions thrown by the HP quad IEEE routines. Dave -- J. David Anglin [EMAIL PROTECTED] National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
