On 01.11.21 18:45, Jakub Jelinek wrote:
Note, if we go the way of C/C++ with -mabi=ieeelongdouble vs.
-mabi=ibmlongdouble choosing between the two ABIs and libgfortran being
ABI compatible with both, then we don't need to bump soname.
Sounds like one major pain solved. I think we should do if it possible.
But, if we don't bump it, we need to keep double double there backwards
compatible (i.e. _r16 etc. being the double double, not IEEE).
Correct. I would actually go for 17 for the IEEE because it is
the larger number, but that is a pure style issue and has no
impact on something that is user visible :-)
When in the future we bump the soname, we can swap those two and
make _r16 newly stand for IEEE quad and _r15 or _r16d or whatever
for double double.
Yep.
We do need to do something about the generated module files, though, to
make programs compiled with one option incompatible with the other ones
on that level.
Or are people expected to get that right? :-)
Best regards
Thomas
