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

IVF 9.1 and x64 funny behaviors?

grg99
Beginner
452 Views

Very nice compiler, but a few funny things:

(1) Right-clicking on VS6 brought up a menu with some nice browsing features like "go to declaration". Which worked about 44% of the time. Now with VS8 all the browsing options seem to be missing. While this eliminates the 66% of errors, I'd rather have the remainder. Is this correct behavior? Did something not install correctly?

(2) When debugging, local variables are often okay, but globals are never findable.

(3) Changing the source code while debugging never causes a rebuild, even with the "always rebuild on changes" option turned on.

(4)

Also a gentle suggestion:

Many of the compiler error messages are quite apropos, helpful, and clear.

But a large minority are along the lines of:

"Somewhere in thisstatement there is a type conflict"

In a perfect world it would be nice to instead get:

"Variable X9 at column 44 seems to be of type "INTEGER(Kind=HighPrecision)" while the expression after it evaluates to type "TYPE(INFUNDIBULUM)" which are irreconcileable due to rule #4 on page 287 of the manual"

Regards,

A_H

0 Kudos
2 Replies
Steven_L_Intel1
Employee
452 Views

(1) The Source Browser feature is not available. It's something we hope to be able to enable in the future. You might want to experiment with setting the "Generate Interface Blocks"(External Procedures)and "Check Routine Interfaces" (Diagnostics) options.

(2) If you mean module variables, use the syntax modname::varname in a QuickWatch window. The absence of host-associated variables is being worked on.

(3) I haven't run into that myself, but I'll do some tests.

(4) Can you provide a real example where you think we can do better?

0 Kudos
grg99
Beginner
452 Views

(4) Can you provide a real example where you think we can do better?

Sure:

(1) " Error: The type of the actual argument differs from the type of the dummy argument. [THINNESS]

It would be nice forit to say:

"The type of the actual argument (You supplied "Infundibulum%Metal%Thickness") differs from the type of the dummy argument. [Dummy Argument Name: Thinness Type: integer(Kind=Skinny)]". Shortened as needed.

-------------------------------------------------------------------

(2) "Error in reading Module [LeatherBikiniInfo]"

It would be nice if it mentioned the kind of error: i.e.:

(a) File not found, looked in .,..Modules,Z:SharedMods

(b) Path not found: Q:JoeSharedMods

(c) Access denied: You are "CrumbBum", R:Jill accessible only by "Team"

-------------------------------------------------------------------

-------------------------------------------------------------------

0 Kudos
Reply