home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!decwrl!deccrl!news.crl.dec.com!dbased.nuo.dec.com!quark.enet.dec.com!lionel
- From: lionel@quark.enet.dec.com (Steve Lionel)
- Newsgroups: comp.os.vms
- Subject: Re: fortran/nohpo?
- Message-ID: <1993Jan24.172352.5424@dbased.nuo.dec.com>
- Date: 24 Jan 93 17:03:25 GMT
- Article-I.D.: dbased.1993Jan24.172352.5424
- References: <8F8C298AB90D201115@NERUS.PFC.MIT.EDU>
- Sender: news@dbased.nuo.dec.com (USENET News System)
- Organization: Digital Equipment Corporation
- Lines: 47
-
-
- In article <8F8C298AB90D201115@NERUS.PFC.MIT.EDU>, MRL@PFC.MIT.EDU
- (Mark London) writes...
- >Can anyone tell me what the /nohpo switch for fortran does, and it what cases
- >do I need to add it, and is there a way to detect via a logical name if it
- >applies the vax I'm using? Thanks.
- >
-
- Ah, someone's been peeking at CLD files, I see. Here's the story. We
- currently have two Fortran compilers for OpenVMS VAX; VAX FORTRAN (current
- version V5.9) and VAX FORTRAN High-Performance Option (FORTRAN-HPO,
- current version V1.3.) The primary audience for FORTRAN-HPO are those
- people with VAX vector processors or multiprocessor systems, as it
- has the ability to do automatic vectorization and/or decomposition for
- parallel processing, though it has a number of other nice enhancements.
-
- The way we sell FORTRAN-HPO is in the manner of an "option" to VAX FORTRAN,
- even though it is a separate compiler. You are required to be licensed
- for VAX FORTRAN and should (but are not required to) have the VAX FORTRAN
- product installed on the system where you have FORTRAN-HPO installed.
- When installed, the FORTRAN command, by default, gives you the FORTRAN-HPO
- compiler. If you want to use the VAX FORTRAN compiler, you use the
- /NOHPO qualifier.
-
- Now it occurred to me that there may be some people who have FORTRAN-HPO
- but choose not to use it for certain applications (though I really don't
- know of good reasons to do so), and that these people might put
- explicit /NOHPO qualifiers in their command procedures. So then I thought
- about what would happen if someone ran these command procedures on
- systems which didn't have FORTRAN-HPO installed; the /NOHPO qualifier
- would result in a DCL command error since the VAX FORTRAN CLD didn't
- define it. So in VAX FORTRAN V5.9, I added /NOHPO as a legal qualifier
- to the FORTRAN CLD, just so that command procedures which use that
- qualifier wouldn't break. The compiler ignores it completely, and
- you shouldn't worry about it if you haven't purchased FORTRAN-HPO.
-
- All of this will become moot when DEC Fortran V6.0 hits the street, as
- it replaces both VAX FORTRAN and VAX FORTRAN-HPO; you will now get the
- vector and auto-decomp features of FORTRAN-HPO at no extra cost. The
- /HPO qualifier is still in the CLD, but is ignored. (As is
- the /CONTINUATIONS qualifier.)
-
- Steve Lionel lionel@quark.enet.dec.com
- SDT Languages Group
- Digital Equipment Corporation
- 110 Spit Brook Road
- Nashua, NH 03062
-