On Sun, Mar 8, 2015 at 6:43 AM, Jerry DeLisle <jvdeli...@charter.net> wrote: > The attached patch fixes this regression
Nice, thanks for working on this! Just out of curiosity, what was the reason for the powerpc failures you had with the previous version of the patch? > and implements KIND=1 and KIND=2 > compatible calls. ... but I'm not convinced this is worth it. As far as I can see, the reason you needed to add the *K symbols to the library is solely to correctly handle the kind=1 and 2 cases, right? However, IMHO kind=1 and 2 integers have too little room for decent precision and for avoiding wraparound anyway. I can see people using the kind=4 version, as that is the default that you get if you don't play around with non-default kinds. I can also see people using the kind=8 version, in order to get better resolution and avoid wraparound. But explicitly using kind=1 or 2, why on earth would anyone do that? So the only reason why we need to support it is because the standard says so. So I would prefer if we just hardcode the error values in the frontend (-HUGE, 0, 0), in case somebody tries to use the kind=1,2 versions, thus also removing the need for the new library functions, keeping the existing simpler ones instead. AFAICT this would be standards conforming. Any other opinions on this? Cheers, -- Janne Blomqvist
