Hi! On Sat, Nov 21, 2020 at 12:37:10AM -0500, Michael Meissner wrote: > Since the test is explicitly checking for IBM extended double, do not try to > run it when long double is IEEE 128-bit.
Before your change, it would explicitly use __ibm128 if that is not the same as long double. You need a better explanation / justification for the patch. What goes wrong without the patch? Is that to be expected? Etc. You get less coverage than before after this patch (it will now only run on systems that have double-double as long double). Segher
