Hi Thomas, > The KIND=17 is a bit of a kludge. It is not visible for > user programs, they use KIND=16, but this is then translated > to library calls as if it was KIND=17 if the IEEE 128-bit floats > are selected
Can you check what the IEEE test results are when -mabi=ieeelongdouble is enabled? It’s not even clear to me what the IEEE kinds selected should be, in this case, depending on -mabi=ieeelongdouble > Regarding FX's patch: I am not quite sure that I am > actually testing the right thing if running the testsuite > there, so POWER should not hold up this patch. If it turns > out that POWER needs additonal work on IEEE, we can always > add that later. Actually, it sounds like the situation is: the same target can have two ABIs based on a compile-time flag. That sounds like a job for multilib, i.e., we should compile libgfortran twice, one for each ABI. I am sure this was considered and rejected, do you remember what was the rationale? Thanks, FX
