https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29969
--- Comment #5 from Oleg Endo ---
(In reply to Oleg Endo from comment #4)
> If this is true, using 64 bit fmov for block moves could be beneficial.
> Still, I'd not enable this by default but allow the user to turn it on
> with an -m option.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29969
Oleg Endo olegendo at gcc dot gnu.org changed:
What|Removed |Added
CC||olegendo at gcc
--- Comment #2 from marc dot mengel at gmail dot com 2010-06-10 16:43
---
This could be a disaster if floating point exceptions are enabled, as it would
trigger an exception whenever some part of the block was an invalid floating
point number.
One would at least need to save/restore
--- Comment #3 from amylaar at gcc dot gnu dot org 2010-06-10 19:58 ---
(In reply to comment #2)
This could be a disaster if floating point exceptions are enabled, as it would
trigger an exception whenever some part of the block was an invalid floating
point number.
One would at
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-11-25 23:36 ---
Confirmed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
