Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Diagnostic Unclear

clayho
Beginner
922 Views

This reflects my lack of understanding of the problem with NAMED COMMON. I have studied all the pdfs but no joy. Just a small clue as where to go to study answer.

clay

0 Kudos
6 Replies
Lorri_M_Intel
Employee
922 Views
Quoting - clayho

This reflects my lack of understanding of the problem with NAMED COMMON. I have studied all the pdfs but no joy. Just a small clue as where to go to study answer.

clay


Can you give a few more details about what problem you are having with named COMMON?I can imagine a couple of possible areas of confusion, but it would be better to have a better description from you.

thanks --



0 Kudos
clayho
Beginner
922 Views

Can you give a few more details about what problem you are having with named COMMON?I can imagine a couple of possible areas of confusion, but it would be better to have a better description from you.

thanks --




I included a screen print file (fortran_help_1.jpg) with the actual diagnostic and coding. I din't know how to access it. clay
0 Kudos
Steven_L_Intel1
Employee
922 Views
See the link in my signature, below, for how to attach a file to a post.
0 Kudos
clayho
Beginner
922 Views
See the link in my signature, below, for how to attach a file to a post.

I think that's what I did. I really ment that I couldn't tell Lorrie how to access it or look at it again myself. Thanks Steve.

clay
0 Kudos
Steven_L_Intel1
Employee
922 Views

Click Add Files and see if you have the folder you created. Open the folder then click on the file you uploaded. Click Add as Attachment.

We can't see your files unless you attach them to a post.
0 Kudos
TimP
Honored Contributor III
922 Views
The warnings about COMMON are just warnings, first, in case the data types aren't used consistently in all instances (which could break your program), second, because of effect on performance.
The errors about argument data types show that you have a serious disagreement between the data declarations in effect at the CALL and those in effect in the called subroutine. In the rare event that this is intentional, there are ways to force your way past it, but it will not be correct and portable. Nearly always, what you must do is make the data types agree on both sides.
0 Kudos
Reply