https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot
com> ---
I wouldn't expect any *if libgcc function names to be used, because "tf"
libgcc names are supposed to refer to the ibm128 format and "kf" names are
supposed to refer to the IEEE binary128 format, regardless of which format
is actually TFmode inside the compiler.
Probably much the same issue as this bug: building
_Complex double ic __attribute__ ((mode (IC)));
void test_ic (void) { ic /= ic; ic *= ic; }
with -mabi=ieeelongdouble produces spurious __divic3 and __mulic3
references (should be __divtc3 and __multc3).
