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

Force loading objects into mixed language IVF

tonyjay68
Beginner
506 Views
History:
In my CVF projects (about 100) I have many libraries containing c++ and f77/f90/fpp files. Some of theses libraries have routines of the same name (parallel development of routines like 'output' etc) I also have block data in my main program.
When I convert to IVF, either fortran or C++ becomes the dominant library. This means that auto conversion of the projects in not adequate as my library objects are not force loaded in the program any more (i.e. if my fortran is the dominant program my C++ gets pushed into a library and then I beleive it is a matter of chance if this object actually gets loaded into the program or a different object of the same name is loaded form another library)
As I have many problems with the intel compiler, I can not use it for day to day work , but just reconvert my projects from CVF from time to time (I still have bug reports not fixed which are 4 months old ;-(, once they are fixedI can dump CVF). I would like to change my CVF projects so that I can reimport to intel without hours of reconfiguring projects.
Currently I can not see how to set up the intel projects at all, let alone how to do it under CVF so it will work on IVF. I have had success force loading the object, rather than the file, by including the object from my c++ library in to the fortran program - but it is unclear how to do this in both both Debug an release modes (as the two objects are different)
AmI missing an obvious solution to a simple problem. Any advice would be gratefully received.
Tony
0 Kudos
2 Replies
g_f_thomas
Beginner
506 Views
Why port from CVF to IVF if it's such a hassel?

Ciao,
Gerry T.
0 Kudos
tonyjay68
Beginner
506 Views

Why ? I keep asking my self the same question. At some point I will have to progress out of the 1990's, perhaps for .net, for 64 bit, f2003, c## or what ever is around the corner. Sticking witha product which is not going to be developed any further (how ever good it is) is not sensible planning. By trying to port to intel when it is not a necessity I hope that their development team can at least fix some of their (my) their problems. When the porting actually works I can then chose whether I want to do it.

I also hope the IVF will get dependancy checking right (compared to my nightmares in CVF) however my first impression (after 6 months) is that it just has different dependancy 'problems'

Tony

0 Kudos
Reply