Re: CVF to Intel USE statements

From: Herman D. Knoble (SkipKnobleLESS_at_SPAMpsu.DOT.edu)
Date: 03/09/05 

Date: Wed, 09 Mar 2005 11:53:57 -0500

Steve: Many thanks.

This is a valuable document. Yep, the information I requested
is given in that document's:
Table 1: Old and New Names of System and Library Modules

It's good to hear that the Premier Support login will be improved.
I was able to login to Premier Support; that alone hopefully will,
in the future, enable me to post to the forums.

We have a 140,000 lines of Fortran 77 mixed with Fortran 90 syntax.
The developer used CVF. I am happy to report that with the
USE DFPORT and USE DFLIB changed to USE IFPORT and USE IFCORE,
changes cited in the Table 1 (from the URL you kindly provided),
the whole thing compiles and links with no errors using the Intel
compiler (for Linux). Impressive! One of the most convenient
conversion crutches provided by IFORT was that it allowed Fortran
90 syntax with source module file extensions of .for . Thus mixing
source modules sytax was quick and easy. Eventually they are
converting all source modules to Fortran 90 syntax; but to
see the conversion issues between CVF and IFORT, allowing
both F77 and F90 syntax with one file extension and suporting
IFORT *.for as a command line made this quick check a lot easier
(I am no fan of Make file:-)

Most likely this research group user will lease the Intel Compiler
for Windows; although we're offering use of our Linux cluster so
that they would have run-access to this code from anywhere in
the world.

Again, Thank you.
Skip

On Wed, 09 Mar 2005 11:09:42 -0500, Steve Lionel <Steve.Lionel@REMOVEintelME.com> wrote:

-|On Wed, 09 Mar 2005 10:41:27 -0500, Herman D. Knoble
-|<SkipKnobleLESS@SPAMpsu.DOT.edu> wrote:
-|
-|>Can someone please point me to a URL that gives all of the CVF to
-|>Intel compiler dependent cross compiler USE statement table - including
-|>the ones available to the Inten Compiler that do not exist in CVF?
-|>(I realize this is an IFORT forum question, but somehow throughout
-|>the several forced changes of Primer Login password, I seem to have
-|>forgotten my password).
-|
-|First, the user forums do not use the Premier Support login info - they are
-|part of Intel Developer Services and have their own login system. (And for
-|those of you who have had problems with Premier Support login requirements,
-|that is supposed to be significantly improved within the next month or so.)
-|
-|Second, look at
-|http://developer.intel.com/software/products/compilers/techtopics/portingcvf1.htm
-|for a document on migrating from CVF to Intel Fortran - it includes a module
-|cross-reference table. However, you typically don't need to change a thing -
-|the CVF module names are still supported.
-|
-|
-|Steve Lionel
-|Software Products Division
-|Intel Corporation
-|Nashua, NH
-|
-|User communities for Intel Software Development Products
-| http://softwareforums.intel.com/
-|Intel Fortran Support
-| http://developer.intel.com/software/products/support/

Relevant Pages

  • Re: CVF to Intel USE statements
    ... >Intel compiler dependent cross compiler USE statement table - including ... >the ones available to the Inten Compiler that do not exist in CVF? ... the user forums do not use the Premier Support login info - they are ... part of Intel Developer Services and have their own login system. ...
    (comp.lang.fortran)
  • Re: bye bye CVF
    ... development team, based on CVF sources, and there are again some who seem to view the transition as some sort of personal betrayal. ... really big plus in favor of IVF when the time comes. ... I'm pleased as punch that the compiler is now derived from DVF/CVF and that the ~DEC/Compaq compiler team is intact and supporting it. ...
    (comp.lang.fortran)
  • Re: Compaq Visual Fortran
    ... it; Steve Lionel. ... Steve moved with the compiler, ... many if not most clinging to CVF will eventually transition to IVF at some point. ... Support the Original G95 Project: http://www.g95.org ...
    (comp.lang.fortran)
  • Re: Acceptable Pack args
    ... NO-ONE SHOWED my "assertion" for CVF was false for the sample program ... OR for any other compiler ... not sure but I believe it was because my function that used PACK was in module that CVF did not issue a conformance error. ...
    (comp.lang.fortran)
  • CVF 6.6.C - 3 /NoXXX Options Not Work (Was: CVF 6.6C Error Message - Negation of /NoF66 swi
    ... I wrote the original message asking about an error message when I used the /NoF66 compiler option with CVF 6.6.C. ... In all three cases, this behavior contradicts the published documentation, which includes the on-line documentation and the Digital Visual Fortran Programmer's Guide by Michael Etzel and Karen Dickenson. ...
    (comp.lang.fortran)