-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
numerical differences in gfortran vs. ifort and release vs. debug #154
Comments
gfortran debug vs ifort release (reference)
End of exception errors
So no difference between debug and release using gfortran. Here's a "summary" of the differences observed for this specific test:
where The most differences occur when anything is compared to ifort release. Fewer differences occur when comparing gfortran to ifort debug. The only one with almost no difference is between gfortran debug and gfortran release. Here's an example of the differences between gfortran release and ifortran release:
And example of differences between gfortran debug vs. ifort debug
Overall these values are tiny, but I wanted to document these. The numerical issue " Floating-point exception - erroneous arithmetic operation." appears to be a "bug" in the float comparison routine, and likely related to underflow. |
This issue captures a longstanding (and generally ignored) issue with CRTM wherein some ctest results will differ when run in release vs. debug. I don't know that there's a clear solution, but given that it only affects certain ctests, suggests that there might be a fix.
The largest difference on the order of 1e-11, so in no way would this impact anything useful.
ifort, Release:
ifort, Debug:
gfortran, Release:
gfortran, Debug:
The text was updated successfully, but these errors were encountered: