--- Comment #7 from ubizjak at gmail dot com 2009-02-03 11:10 ---
Not a GCC bug.
--
ubizjak at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRMED
--- Comment #6 from abramobagnara at tin dot it 2009-01-24 15:41 ---
(In reply to comment #5)
> Because it looks to me that this is libc problem with fetestexcept. As far as
> the compiler is concerned, GCC correctly decorates trapping instructions with
> /sui and puts trap barrier to e
--- Comment #5 from ubizjak at gmail dot com 2009-01-24 10:17 ---
(In reply to comment #4)
> I don't know why the bug was closed: I can confirm the erroneous behavior is
> present also in GCC 4.3.2.
Because it looks to me that this is libc problem with fetestexcept. As far as
the compil
--- Comment #4 from bagnara at cs dot unipr dot it 2009-01-24 08:08 ---
I don't know why the bug was closed: I can confirm the erroneous behavior is
present also in GCC 4.3.2.
--
bagnara at cs dot unipr dot it changed:
What|Removed |Added
-
--- Comment #3 from abramobagnara at tin dot it 2009-01-24 05:43 ---
The test case you have used it's different from the original that showed the
bug.
Nevertheless it's useful to understand the possible nature of the bug.
It seems that if feenableexcept(FE_INEXACT) is not called
fetest
--- Comment #2 from ubizjak at gmail dot com 2009-01-23 08:47 ---
Works for me with:
--cut here--
#define _GNU_SOURCE
#include
#include
#include
static void foo (int sig)
{
exit (0);
}
float __attribute__((noinline)) test (float x) { return 2.0f / x; };
int main()
{
volatile f
--- Comment #1 from bagnara at cs dot unipr dot it 2008-09-19 07:04 ---
Created an attachment (id=16359)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16359&action=view)
Assembly code generated with g++ -S -mieee-with-inexact sf.cc
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?i
