On Wed, 4 Jun 2014, Jason Merrill wrote:
How about, in emit_support_tinfos, using type_for_mode to check for a TF-mode floating point type different from long_double_type_node?
What should I pass as the mode argument? I can't just write TFmode, that will fail to compile on platforms that don't define it, and powerpc seems likely to call it JFmode instead quite soon. MAX_MODE_FLOAT maybe? But then if we configure with long double = __float128, we will miss __float80.
Ah, we walk from GET_CLASS_NARROWEST_MODE (MODE_FLOAT) with GET_MODE_WIDER_MODE steps and test if the associated type is not in the list 0/float/double/long double. I think it should be ok with arm (it would be good if they removed their unused XFmode, but I don't even think it is necessary).
Is that what you were suggesting? I'll try to write a patch, thanks. -- Marc Glisse
