My company is migrating from Fortran 10 to Fortran Composer XE 2013 and we're getting multiple failures in our regresssion tests. Many working hours were spent in attempts to localize the source of errors until we noticed that the option /nofltconsistency was default. After setting it to /fltconsistency all errors went away.
I understand the striving to make compiler code faster but why to do this at the expense of accuracy? Developers of source codes from netlib.org worked in XX century when no one could divine what the future with /nofltconsistency will be like. I also understand the importance of RTFM but information about /fltconsistency is buried deep in user guide: Compatibility and Portability/Understanding Fortran Language Standards/Using Compiler Optimizations.
I'd suggest to make /fltconsistency default option for future updates and to improve visibility of this option in documentation.