- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Could someone tell me how I can specify that a specific warning message issued by the forrtl be suppressed. In particular, when I run my program, I see endless messages such as this:
forrtl: warning (402): fort: (1): In call to SETRAYINFO_INFO, an array temporary was created for argument #3
If this isn't possible, is there a way I can suppress all forrtl warning messages but still see messages of a higher severity?
Thanks for your attention.
Norm Clerman
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That message is not enabled by default. It is controlled by /check:arg_temp_created. If you simply said /check or enabled all run-time diagnostics, you'll get that one too.
However, it is a useful message that indicates a possible performance issue in your application. It may be that you cannot avoid the copy, but it is worth looking at. This message is given when you pass a non-contiguous array or array section to a routine which expects a contiguous array.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That message is not enabled by default. It is controlled by /check:arg_temp_created. If you simply said /check or enabled all run-time diagnostics, you'll get that one too.
However, it is a useful message that indicates a possible performance issue in your application. It may be that you cannot avoid the copy, but it is worth looking at. This message is given when you pass a non-contiguous array or array section to a routine which expects a contiguous array.
Hi Steve,
Thanks. Actually, I think the cause of the message is a call like this:
CALL MySub (arg1, [data(1), 0.0], arg3, arg4)
It's been working fine for years, and I don't think it's causing a performance hit.
I really needed to kill it, and now I know how.
Thanks for you help.
Norm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, Hi, Norm. I didn't pick up on it being you.
In the case you cite, it's not a problem. The compiler HAS to create a temporary array for that array constructor.

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