Dear Harald, On 9/14/20 10:01 PM, Harald Anlauf wrote:
OK for master?
I think we should fix this properly by using target hooks as suggested by Joseph in the PR. Otherwise, I have no idea how one could handle this properly on the FE side for PowerPC (see below). Tobias PS: from gcc/config/rs6000/rs6000-modes.*: /* IBM 128-bit floating point. */ FRACTIONAL_FLOAT_MODE (IF, FLOAT_PRECISION_IFmode, 16, ibm_extended_format); /* Explicit IEEE 128-bit floating point. */ FRACTIONAL_FLOAT_MODE (KF, FLOAT_PRECISION_KFmode, 16, ieee_quad_format); /* 128-bit floating point, either IBM 128-bit or IEEE 128-bit. This is adjusted in rs6000_option_override_internal to be the appropriate floating point type. */ FRACTIONAL_FLOAT_MODE (TF, FLOAT_PRECISION_TFmode, 16, ieee_quad_format); /* We order the 3 128-bit floating point types so that IFmode (IBM 128-bit floating point) is the 128-bit floating point type with the highest precision (128 bits). This so that machine independent parts of the compiler do not try to widen IFmode to TFmode on ISA 3.0 (power9) that has hardware support for IEEE 128-bit. We set TFmode (long double mode) in between, and KFmode (explicit __float128) below it. We won't encounter conversion from IEEE 128-bit to IBM 128-bit because we don't have insns to support the IBM 128-bit aritmetic operations. */ #ifndef RS6000_MODES_H #define RS6000_MODES_H 1 #define FLOAT_PRECISION_IFmode 128 #define FLOAT_PRECISION_TFmode 127 #define FLOAT_PRECISION_KFmode 126 ----------------- Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
