--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Severity|major |normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35709
--- Comment #1 from sergstesh at yahoo dot com 2008-03-26 19:23 ---
Created an attachment (id=15383)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15383action=view)
the test case
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35709
--- Comment #2 from sergstesh at yahoo dot com 2008-03-26 19:40 ---
My system:
Linux amdam2 2.6.18.8-0.9-default #1 SMP Sun Feb 10 22:48:05 UTC 2008 i686
athlon i386 GNU/Linux
- SUSE 10.2, the CPU is: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
stepping 02.
--
--- Comment #4 from sergstesh at yahoo dot com 2008-03-26 20:44 ---
(In reply to comment #3)
This was an intentional change for correctness. 4.3 uses the library
implementation to handle the case of NaNs correctly. Use -fcx-limited-range
if you want back the performance.
Well,
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-03-26 20:45 ---
As mentioned, use -fcx-limited-range.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35709
--- Comment #6 from sergstesh at yahoo dot com 2008-03-26 20:58 ---
(In reply to comment #5)
As mentioned, use -fcx-limited-range.
Can't you add just _one_ command line switch: -old_behavior ?
Or -gcc_4_2_3_behavior ?
For example, I need FFTW3 with float rather than double, and I
--- Comment #7 from rguenth at gcc dot gnu dot org 2008-03-26 22:22 ---
I would suggest for real time audio you should use -ffast-math which will
enable
-fcx-limited-range as well. It also disables generally handling of NaNs, Infs
and other optimization limiting things.
--
