https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61399
--- Comment #13 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- (In reply to Jakub Jelinek from comment #12) > That isn't representable in the GCC internal representation, which pretends > the type has fixed 106 bit precision [...] So, if I understand correctly, this is due to a limitation of GCC internals. > The only way around that would be to actually represent it in GCC internal > representation as sum of two doubles and rewrite all operations on this mode > to treat it specially. That is a lot of work and given that powerpc64le is > switching from this floating point format to IEEE quad long double format, > I'm certain nobody is willing to spend that much time (months) on it. Well, if there is a difficulty of implementation, perhaps leave LDBL_MAX as is, and consider for instance that an operation that with the result 0x1.fffffffffffff7ffffffffffffcp+1023 would overflow (which is AFAIK undefined behavior for non-IEEE-754 formats, so that this would be conforming). But this should be documented.
