Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Double precision vs. REAL(KIND=8)

DavidWhite
Valued Contributor II
1,159 Views
I'm clutching at straws here. A major app has just gone off the rails - main change that I can see between versions is that I changed all previous references to Double precision to Real(KIND=8).

What changes can I expect in data values with this change? I certainly was not expecting any.

The error appears to be in the rkf45/rkfs/fehl set of codes which were written f77 style, and I changed all the references to Double Precision.

Previous version was compiled with latest compiler as at 24 September, latest version compiled with 2011.1.127.

Compiler command line is
/nologo /debug:minimal /Oy- /I"C:\\Dev\\Winyldmd Dev\\trunk\\ymd_modules\\..\\..\\..\\Modules\\Release" /I"C:\\Dev\\Winyldmd Dev\\trunk\\ymdphys\\..\\..\\..\\modules\\Release" /I"C:\\Dev\\VerCheck\\..\\modules\\Release" /I"C:\\Dev\\Winyldmd Dev\\trunk\\PSDMod\\..\\..\\..\\Modules\\Release" /I"C:\\Dev\\Winyldmd Dev\\trunk\\ymd_commands\\..\\..\\..\\modules\\release" /I"C:\\Dev\\Winyldmd Dev\\trunk\\ymdutils\\..\\..\\..\\Modules\\Release" /Qopenmp /warn:declarations /warn:unused /fpe:0 /module:"..\\..\\..\\Modules\\Release" /object:"..\\..\\..\\Intermed\\Release/" /traceback /check:bounds /check:uninit /check:format /libs:static /threads /c

Thanks,


David
0 Kudos
1 Reply
Steven_L_Intel1
Employee
1,159 Views
Try adding /warn:interface. Unless you also use /double_size, there should be no effects from making that specific change.
0 Kudos
Reply