The <limits> header defines default values for NaN-related booleans and values, but no machine-specific config file overrides the defaults, that are not appropriate for say x86. I realize the implementation in say gcc 3.4 relies on a number of compiler built-ins (macros and functions) that are probably too much risk or work to back-port, but we could simply hard-code the correct definitions for the macros in machine-specific headers for the platforms we support.
FYI <limits> re-write took place between 3.2.x and 3.3.x. Alexandre's original point, however, that hand-edited bit can get put in the file on a per-target basis. -benjamin
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.