How to include compiler diagnostic warnings in mex fortran files?

My problem is the following:
I use an old fortran code for numerical integration, which is called through a computational routine of a mex Function.
I have tested the fortran code externally, using a main fortran file, via Visual Studio. Because the code is old, the only way that I can compile and run it successfully is if I enable /warn:[no]interfaces option of the ifort compiler.
Now, I am trying to "attach" this fortran code to a mexFunction. The getaway function works fine and the standard mex compilation is successfull. But, when I run the mex64 output function, MATLAB craches unexpectedly. Thus, I think that I somehow need to incorporate the /warn:[no]interfaces flag in standard mex compilation. I tried using COMPFLAGS='$COMPFLAGS /warn:[no]interfaces' but there was no such option.
I would appreciate any suggestions. Thanks in advance

[Dolon Mandal]

Can you please try the following:

1. Locate the `mexopts.sh` file on your system. This file contains the compiler options used by MATLAB's `mex` command.

2. Open the `mexopts.sh` file in a text editor. Look for the section that defines the `CFLAGS` variable. This variable contains the compiler options for C code. Add the `/warn:[no]interfaces` flag to the `CFLAGS` variable. The modified line should look something like this:

CFLAGS="$CFLAGS -warn:[no]interfaces"

4. Look for the section that defines the `CXXFLAGS` variable. This variable contains the compiler options for C++ code. Add the `/warn:[no]interfaces` flag to the `CXXFLAGS` variable. The modified line should look something like this:

CXXFLAGS="$CXXFLAGS -warn:[no]interfaces"

5. Save the `mexopts.sh` file.

[James Tursa]

Is the [no] part supposed to indicate this is optional text? I.e., the available options are interfaces and nointerfaces? At least that is what [ ] typically means.

[Dimitrios Patsatzis]

Dear Dolon,

Thanks for you reply.

Unfortunately, there is no mexopts.sh file on my system to configure. However, I tried compiling by appendig the -warn:[no]interfaces flag in matlab command; i.e., mex CXXFLAGS='$CXXFLAGS -warn:[no]interfaces' CFLAGS='$CFLAGS -warn:[no]interfaces' filename.f

Compile is again succesfull, but when running mex64 output function, matlab is crashing.

Thanks for the help!

Dear James,

I used this flag for the ifort compiler in visual studio, so that I make sure the fortran source code is not crashing (before incorporating in Matlab). I do not know what exactly it does, but with the [no] argument, it supresses some warnings that newer versions of fortran throw out (the original code is a package written in fortran77).

Thanks for your reply in any case.

[dpb]

@James Tursa is correct -- the actual switch value is either "interfaces" or "nointerfaces"; the [no] is simply the documentation to indicate the alternate "no" state.

However, turning off interface checking warnings will simply keep the compiler from checking each function/subroutine against an external set of interface blocks, it will NOT change anything in the compilation/generated object file. If the mex file crashes, that says something isn't correct, probably while the gateway function compiles, a pointer issue is generally the most common cause.

That you don't have interfaces is an easy way for a mismatch in arguments to exist and not know about it until run time; it's possible you're finding a bug that has been hidden all along, although if it does work with Fortran main program, the likelihood (but not guaranteed) is that the issue is in the gateway routine interface to the called function, not in the internal calling sequences.

[dpb]

Add the `/warn:[no]interfaces` flag to the `CXXFLAGS` variable. The modified line should look something like this:

CXXFLAGS="$CXXFLAGS -warn:[no]interfaces"

No. The line should be

CXXFLAGS="$CXXFLAGS -warn:nointerfaces"

The [] simply indicate an optional state; they are not part of the switch value.

However, <the Intel doc says> that 'nointerfaces' is the default state anyways...

[dpb]

OBTW, @James Tursa is the Fortran mex guru; post your Fortran code calling sequence including enough to tell what are all data types and your gateway routine; odds are good that he would take a look at it and find any problems there.