------- Additional Comments From tromey at gcc dot gnu dot org 2005-08-23
14:15 -------
I see this too.
Compiling with -fno-bounds-check helps, but not enough.
One possibility is simply that our implementation of nextDouble is
inefficient. I doubt this function was coded for maximum performance.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2005-08-23 14:15:25
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23283
