Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

MIgrating from CVF to IVF

Matthaios_Antoninis
462 Views
Hello
I am working on an academic code (thats why I can not show the code in this forum) pre- designed in CVF now we are trying to transform it to IVF (Intel visual fortran Composer XE 2011 update 8) I read the article for the mirgation from CVF to IVF but I have some questions.
(contains 40 .f,f90 files , library files .lib and .inc (common blocks))
1. the conversion uses from CVF .dsw and .dsp files to create the new project containing all the files .f,.f90,.lib and compiled all the files without errors, but I take "compilation" errors while linking
1a. the common blocks .inc files where we add them ? simply adding to the source file as existing files ?
1.b the great difference facing If I tried to create a new project from scratch adding the same files in Source folder I get compilation errors that with the conversion didnt exist. (arguments in functions, include paths, ... )That's why I suppose that there are some options into the compiler that are neccessary and are imposed from the conversion automatically. PLease inform me for this options , I need them for reasons that I will explain below.
2. if you need some .lib files I suppose that these are alreday compiled (as the compiler try to find the compiled module "X".mod from "X".lib file) you face the problem with the linker of cannot opening old libraries such as LIBC.LIB or dfor.lib which means that some files are precompiled with the old CVF compiler, then how you can compiled them with IVF ? I have faced this problem and I see all the .obj files modfied now however I face the same errors. that's why I suppose that it is better to start the project as smth new tottally to be sure that there is nth compiled in CVF. If you have another opinion please make me know.
3. In the case that you simply add the files (without conversion) you receive errors for "include" paths for modules that coexist in the same project and the message says that can not find the compiled module 'X' (to "Use X" statement). Why try to find smth compiled ? as the file - module exist in the same project
Many thanks for your patience in advance.
0 Kudos
1 Reply
Steven_L_Intel1
Employee
462 Views
All .lib files compiled with CVF must be recompiled with Intel Fortran. No exceptions. This is why you are getting references to LIBC.LIB and DFOR.LIB.

Module files (.mod) are independent from library files (.lib), though you may generate .mod files while building libraries. All Fortran sources for .mod files from CVF must be recompiled by Intel Fortran.

You do not need to add INCLUDE files to your project, but you can do so if you want. It is best to add them to the "Header Files" folder in the project.

Intel Fortran does more extensive error checking than CVF did, so that is why you get errors about function arguments. You should fix the errors it points out.
0 Kudos
Reply