[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2020-02-08 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 --- Comment #9 from Rich Felker --- Indeed, I don't think the ABI says anything about this; a bug against the psABI should probably be opened.

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2020-02-08 Thread vincent-gcc at vinc17 dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 --- Comment #8 from Vincent Lefèvre --- (In reply to Rich Felker from comment #7) > Note that such an option would be nice to have anyway, for arbitrary > functions, since it's necessary for being able to call code that was > compiled with -fexce

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2020-02-07 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 --- Comment #7 from Rich Felker --- I'll inquire about it. Note that F.6 already requires this for C functions; the loophole is just that the implementation itself does not inherently have to consist of C functions. If it's determined that C won

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2020-02-07 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 --- Comment #6 from joseph at codesourcery dot com --- Do you have any reference to a proposal to that effect? The current wording in N2454 regarding this says "IEC 60559 requires operations with specified operand and result formats. Therefor

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2020-02-06 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 Rich Felker changed: What|Removed |Added CC||bugdal at aerifal dot cx --- Comment #5 fr

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2017-09-26 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 --- Comment #4 from joseph at codesourcery dot com --- I think the glibc reasoning is: libm functions do not need to behave as if written in standard C, so in particular F.6 does not apply to them and they may return values with excess precisio

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2017-09-25 Thread vincent-gcc at vinc17 dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 --- Comment #3 from Vincent Lefèvre --- (In reply to Andrew Pinski from comment #1) > This is interesting because log2 should have already done a rounding to > double before returning. I suppose that if the C library has been built with GCC with

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2017-09-24 Thread zimmerma+gcc at loria dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 Paul Zimmermann changed: What|Removed |Added CC||zimmerma+gcc at loria dot fr --- Comme

[Bug c/82318] -fexcess-precision=standard has no effect on a libm function call

2017-09-24 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82318 Andrew Pinski changed: What|Removed |Added Keywords||wrong-code Target|