[Bug libgcc/104253] libgcc missing __floatdiif

2022-01-27 Thread meissner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 Michael Meissner changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug libgcc/104253] libgcc missing __floatdiif

2022-01-27 Thread meissner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 --- Comment #4 from Michael Meissner --- Created attachment 52306 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52306=edit Patch to use the correct names for __ibm128 converts if long double is IEEE 128-bit The problem was internally

[Bug libgcc/104253] libgcc missing __floatdiif

2022-01-26 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[Bug libgcc/104253] libgcc missing __floatdiif

2022-01-26 Thread joseph at codesourcery dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 --- Comment #2 from 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

[Bug libgcc/104253] libgcc missing __floatdiif

2022-01-26 Thread meissner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 Michael Meissner changed: What|Removed |Added Last reconfirmed||2022-01-26