- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can report the problem using the Intel Online Service Center, attaching a copy of the program source, instructions for building, and including any data files it needs. (A tarball works.) What you have said here is too vague for any of us to be helpful. It sounds to me as if ifort 18 is the issue, not the MacOS version. It might be an issue with the gcc libraries Apple makes available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for the reply and advice. But I need to ask for the permission of upload the program. Because it is from my supervisor and I just made some modifications. It is the copy right issue. And I am not sure about the results yet.
You mentioned the gcc libraries issue. So can you guide me to do some try by myself? In fact, I am also a beginner of command stuff and fortran.
Steve Lionel (Ret.) wrote:
You can report the problem using the Intel Online Service Center, attaching a copy of the program source, instructions for building, and including any data files it needs. (A tarball works.) What you have said here is too vague for any of us to be helpful. It sounds to me as if ifort 18 is the issue, not the MacOS version. It might be an issue with the gcc libraries Apple makes available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, I've exhausted my Mac knowledge. All I know is that the Intel compiler requires that gcc be installed so that its libraries can be used, and that Apple no longer installs these by default. But the gap between the 14 and 18 compilers is large. It may come down to a different sequence of code that reveals an instability in your program's algorithm. It could be improvements in the math library giving different results.
If you can't yet provide Intel with the program, you might at first try disabling optimizatioins and see if that changes the behavior. If it does, that doesn't necessarily mean the compiler is wrong.
What I would do is "instrument" the program to show you intermediate results and progress. Build and run it with both compilers and see where behavior starts to diverge. That will tell you a lot.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page