home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!hal.com!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: <1993Jan25.142105.15974@dbased.nuo.dec.com>
- Date: 25 Jan 93 14:21:05 GMT
- References: <8F8C298AB90D201115@NERUS.PFC.MIT.EDU>,<1993Jan24.172352.5424@dbased.nuo.dec.com> <1993Jan25.063529.15242@iscnvx.lmsc.lockheed.com>
- Sender: news@dbased.nuo.dec.com (USENET News System)
- Reply-To: lionel@quark.enet.dec.com (Steve Lionel)
- Organization: Digital Equipment Corporation, Nashua NH
- Lines: 29
-
-
- In article <1993Jan25.063529.15242@iscnvx.lmsc.lockheed.com>,
- marshall@NEBULA.SSD.LMSC.LOCKHEED.COM (Bob Marshall) writes:
- |>
- |>One of the FAQs at my site is "what does it mean when I compile my
- |>program and I get the message 'COMMON block not naturally aligned'?".
- |>After attempting to explain what it means, if the querant does not
- |>appear to be satisfied (which is usually the case), my next response is
- |>"if it bothers you, just use the /NOHPO switch". In many cases they are
- |>compiling on a uniprocessor system in our system which has no vector
- |>processor, anyway.
- |>
- |>So, there's at least one situation where the /NOHPO switch makes sense,
- |>even when the FORTRAN-HPO compiler is available.
- |>
-
- I'd think that /WARNINGS=NOALIGNMENT would be a better suggestion. That's
- one thing I've changed in V6, though - you won't get alignment warnings by
- default. We do recommend that you specify /WARNINGS=ALIGNMENT if you're
- using vector processing, considering porting to Alpha AXP, or just want the
- best performance on the VAX (as unaligned memory accesses are slower on VAX.)
-
- --
-
- Steve Lionel lionel@quark.enet.dec.com
- SDT Languages Group
- Digital Equipment Corporation
- 110 Spit Brook Road
- Nashua, NH 03062
-