https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38960
--- Comment #6 from rguenther at suse dot de ---
On Fri, 4 May 2018, joseph at codesourcery dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38960
>
> --- Comment #5 from joseph at codesourcery dot com dot com> ---
> Since any non
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38960
--- Comment #5 from joseph at codesourcery dot com ---
Since any non-const function can examine floating-point state, I'd expect
significant effects on code generation. (Whether this also applies to
asms depends on the architecture; some archi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38960
--- Comment #4 from Richard Biener ---
Note that a not too disruptive "implementation" of the dependences would be
to add outgoing abnormal edges to the fenv* calls. Not too
disruptive in terms of implementation - the effect on code generation m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38960
Richard Biener changed:
What|Removed |Added
CC||jtaylor.debian at googlemail
dot c
--- Comment #2 from rguenth at gcc dot gnu dot org 2009-01-24 15:43 ---
It is both due to missing #pragma STDC FENV_ACCESS
GCC does not have a way to represent use/def of floating-point status, so
the call to fetestexcept is not a barrier for moving floating-point
operations. In fact,
--- Comment #1 from abramobagnara at tin dot it 2009-01-24 15:14 ---
Created an attachment (id=17176)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17176&action=view)
Assembler generated by gcc -S -O2 bug.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38960
