Avoiding warnings

[Dieter Britz]

In a program compiled by Intel's Fortran 95, I get a whole lot of
warnings,

forrtl: warning (402): fort: (1): In call to I/O Write routine, an array
temporary was created for argument #1

I want array-bounds and I would like to suppress these warnings
as well, as they are not telling me about anything important.
I compile with

ifort -C -w ...

but the warnings come anyway. How can I suppress them but keep the
array bound check?

--
Dieter Britz

[Arjen Markus]

You can achieve that with the /Qdiag-disable:<number> option,
where <number> is for instance 402, the warning number in your example.

[lwme...@gmail.com]

You can use the explicit -check bounds command line switch, instead of the meta switch -C which sets many of the "-check XX" keywords.

Or, you can keep -C but explicitly turn off messages about temporary arguments with -check noarg_temp_created

--Lorri

[Steve Lionel]

On 12/30/2013 5:36 AM, Arjen Markus wrote:
> You can achieve that with the /Qdiag-disable:<number> option,
> where <number> is for instance 402, the warning number in your example.

Not in this case. As Lorri says, this run-time warning comes from the
use of -C, enabling all run-time checks including arg_temp_created.

--
Steve Lionel
Developer Products Division
Intel Corporation
Merrimack, NH

For email address, replace "invalid" with "com"

User communities for Intel Software Development Products
http://software.intel.com/en-us/forums/
Intel Software Development Products Support
http://software.intel.com/sites/support/
My Fortran blog
http://www.intel.com/software/drfortran

Refer to http://software.intel.com/en-us/articles/optimization-notice
for more information regarding performance and optimization choices in
Intel software products.

[Arjen Markus]

On Monday, December 30, 2013 6:43:23 PM UTC+1, Steve Lionel wrote:
> On 12/30/2013 5:36 AM, Arjen Markus wrote:
>
> > You can achieve that with the /Qdiag-disable:<number> option,
>
> > where <number> is for instance 402, the warning number in your example.
>
>
>
> Not in this case. As Lorri says, this run-time warning comes from the
>
> use of -C, enabling all run-time checks including arg_temp_created.
>

Ah, I tried it with a small program that had a completely different type of warning (actually it was a remark) and erroneously assumed it would work with any type of warning.

Regards,

Arjen