- 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, there are some issues here that I was not aware of so thank you for bringing those to our attention.
As you noted, -show does not function with mpiifort at all. Another issue exists when using ifort where -show does not honor the equal sign separator, so either the option is not behaving as advertised or the documentation is incorrect. It does function with ifort without the equal sign separator.
Hopefully you can use -list only with mpiifort for now to help find the information you were seeking.
I will notify our Documentation and/or Development teams about the issues and update this post with internal tracking id soon.
(Internal tracking id: DPD200374890 - Correct -show documentation to remove equal sign connector)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try enquoting:
mpiifort -r8 -list -"show=map" -c filename.f90
Or some variation on this.
Jim Dempsey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
First, the ifort -show option does not use the equal sign connector as documented so we will correct our documentation in a future release.
Second, I discovered the issue with -show stems from mpif90 (et. al.) actually having its own -show option; thus, the troubles we experienced relate to that.
$ mpiifort -help | grep show
-show show command lines without real calling
Some good news is that I found a way around this using the mpif90 (or mpiifort) -fc= or -f90= option. I found it works to provide the ifort options within the expected string argument as follows:
mpiifort -fc="ifort -list -show nooptions" hello_mpi.F90
I don't know what the general consensus would be for using that, and whether it merits modifying either the mpif90 (et. al.) wrappers or ifort driver to deal with the option name conflict. I'm inquiring internally but if you have thoughts let me know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The advice I received is the usage of the MPI compiler wrapper options (-{cc,cxx,fc,f77,f90}=<compiler> ) is the recommended method for changing the underlying compiler, providing extra options, and (as in this case) avoiding option overlap with an MPI compiler wrapper.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page