Try the CVF 6.5A update

Try the CVF 6.5A update

I'm giving forum readers first crack at trying the CVF 6.5A update (for X86 right now - Alpha version will follow). The software itself is "frozen", this is just to make sure that the update process itself works for most people. Naturally, this is only for people already running CVF 6.5.

Download and run CVF-X86-65A.exe Please report any problems here, or let me know that it worked ok. After installing, try rebuilding your application and viewing the online documentation.

This update is suitable for Standard and Pro edition users, and will update Pro-only bits if you have them.

If all goes well, I'll release the final updates next week.

Steve

Steve - Intel Developer Support
33 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

For those of you who saw my message about pulling the update - sorry. A new copy has been placed at the above location (if it seems to be unavailable, wait a half hour and try again). This one should be ok. Again, let me know how it works for you.

Steve

Steve - Intel Developer Support

Worked OK for me. Tried out simple console and moderately complicated quickwin applications. Noted: (i) splash screen in Dev Studio still says version 6.5, but about-box shows 6.5A; (ii) executables now slightly larger, by up to 12Kb, which may be important to some people.

David Jones

Steve,

I ran the upgrade to upgrade my VF 6.5 standard edition. A couple of things of note:
1) If you have a file called upgrade.exe in the same folder as CVF-X86-65A.exe, it runs that instead of starting the upgrade process. Solutions - delete upgrade.exe or put the VF upgrade in an empty folder.
2) I had the Visual Studio SP4 fix installed with my copy of VF 6.5, the upgrade pops up a message box telling you that SP4 is installed and it needs to apply a fix (again?). I found this a bit confusing.

Apart from that it looks like the compiler and the help have upgraded OK.

Mark.

Worked OK for me (6.5 professional, AC++, WinNT) as far as I can see. Executables now slightly larger, e.g. around 10 k. for a simple console application and 20 k. for a quick win application, both having a size around 600kb.
curt

Thanks for the feedback.

I had thought that WinZip unpacked to a temporary folder - interesting. I'll rename UPGRADE.EXE to be something less generic and this should solve that problem.

I was unaware of an increase in the size of executables - will check into that.

Regarding the SP4 fix - yes, the 6.5A update has to reapply it.

The splash screen doesn't change for "letter" updates.

Steve

Steve - Intel Developer Support

I had no problem upgrading to CVF 6.5a running on Win98.
I had also no problem rebuilding and running several console and windows applications. Also the once that showed problems after upgrading from 6.1a to 6.5 now build and run OK

Walter Kramer

The increase in size is due to some significant new functionality, including new run-time diagnostics (such as "array temp created") that required new support in the RTL, and expansion of NAMELIST to support array slice notation.

On our "to do" list is a restructuring of the RTL so that fewer unused modules get pulled in - thus reducing the size of many statically-linked programs.

If executable size is an issue, consider linking against the DLL libraries.

Steve

Steve - Intel Developer Support

I was able to successfully apply the update under Windows 2000 and Windows 98. I rebuilt a console application under Windows 98 without any problems.

Mike Durisin

I'd appreciate everyone trying out the online documentation from within Developer Studio. Let me know if you see any problems. Thanks.

Steve

Steve - Intel Developer Support

I looked at a few pages of on-line documentation, and everything seemed to be fine.

Mike Durisin

I have had a small problem with the Help facility. I printed off a few pages, using the "heading and all sub-topics" option and found that the Help window was frozen after the print dialogs were complete. This could be unfrozen by clicking on the Help-window's tab on the task bar. The print appeared on the printer OK.

A little more testing has shown that this is repeatable if the thing printed is the collection of headings under "Using the Resouce editor to Design a Dialog" (under "Using Dialogs" in the Programmer's Guide), but not for other equivalent groups of items that I tried ... maybe someting in what is being printed (includes various screen shots) is having an effect.

This is on NT4 (dual processor). The Help control window says version 4.73.8412 and my IE is at version 5.50.4522.1800 (SP1).

David Jones

Steve, How large is the file as it's taking a long time to download?

Thanks, David

The upgrade simply replaced a couple of the documentation files - it doesn't touch the help facility itself, so I doubt the printing problem is related.

The upgrade is about 9MB.

Steve

Steve - Intel Developer Support

Hi Steve,

I've been a bit short of time lately, but I got a chance to apply the update to a NT4 install of CVF 6.5 and just had time to take a brief look. I noticed that while the 'Fortran COM Server App Wizard' was updated, the Fortan COM Server Wizard (csaddin.dll) was not; it should have been, no? There were no errors in the cvf65aupg.log file and csaddin.dll was not listed as one of the 17 files patched in the COM Server Wizard patch component (csw655ai.rtp).

I briefly looked at the release notes and the online docs. Now, I didn't look too deeply, but at first blush it seemed that the docs were a little light on the whys of the new compiler options/attributes.

That's the only 2c I have right now. Thanks,
John

John,

Good catch! Even Leo didn't notice that! I'll fix that for the final version.

Steve

Steve - Intel Developer Support

Steve,
I've (finally!) gone from 6.0A directly to 6.5A (having purchased the 6.5 CD-ROM, of course), so I don't know if this is a 6.5A-related or other difference.
In my QuickWin FPS-compatible program I used
OPEN(UNIT=2,FORM='UNFORMATTED')
to open a scratch file for input and output. And it worked very nicely behind the scenes, totaly unknown to the user.
Now, the user gets prompted for the file to use for Unit 2. Who cares? Gimme a scratch.
Perhaps the new compiler is more rigorous, and I'm supposed to really learn the language? ;)

I have found the upgrade worthwhile in another aspect: it has caught several more "used before defined" things which have been there forever.

Thanks for the good job!
God bless!
Jack

A small thing I noticed was that the update to Array Visualizer has not changed the text in the start menu from Digital Array Visualizer 1.0 to "Compaq" and "1.5". Possibly you were not trying to do so.

David Jones

Jack,

Do you by any chance have a FILE='' in that OPEN? If so, then the behavior you are seeing is what I would expect. If not, it isn't - and I'll ask you to please send a problem description and a ZIP file of your workspace to us at vf-support@compaq.com

David, the upgrade doesn't change the start menu. I agree that it should, and will try to have that done in future upgrades.

Steve

Steve - Intel Developer Support

I have removed the "pre-release" copy of the update and put the final (I hope) copy here. If you installed the "pre-release" version, please first download and run this small patch and then download and run the final version from the above link. If you don't run the small patch first, you will run into trouble in future updates.

An Alpha version will follow in a day or two and then I'll announce it on the web site. Thanks for all your comments and testing.

Steve

Steve - Intel Developer Support

Steve,
I've sent the bug report on the OPEN() problem. There was no "FILE=" of any kind.
A couple of additional very minor items:
The Add/Remove Programs list still says "Visual Fortran 6.0" and "Array Visualizer 1.0" -- perhaps your Setup could clean this?
Also, your bugreport still says to send it to Dvf-support...
Will try the brand-new "final" update momentarily.
God bless!
Jack

Jack,

You didn't send source with your problem report.

The upgrades don't touch the start menu. I agree they should.

Looks like I never had the upgrade replace BUGREPRT.TXT. The old address still works.

Steve

Steve - Intel Developer Support

Steve,
Thanks so much for the speedy vf-support solution/workaround to specify STATUS='SCRATCH' on that OPEN() problem.
Strange I was the only one who noticed -- maybe everyone else is too professional to leave anything unspecified any more, but I'm just an old engineer who happens to need to program to get my work done. The "old" is getting more sincere all the time: been at this computing thing for 35 years, now .. and at this same simulator program for 34 of those.

Thanks again for your great support, as usual...and of course,
God bless!
jack
Jack

The Alpha version of the update is now available.

  1. Create a temporary folder and download CVF-ALPHA-65A.exe into that folder.
  2. Run CVF-ALPHA-65A.exe to unpack the files.
  3. From a command prompt in that folder, use the command "upgrade -l" to start the update.

You can delete the temporary folder afterwards if desired.

As usual, let me know if there are any problems. This will get announced on our web site in the next day or two.

Steve

Steve - Intel Developer Support

Couldn't find it in ftp.compaq.com/pub/products/fortran/vf nor in the supp directory.

Grumble! Sorry about that - will see what's going wrong with the FTP site publishing process. This has usually worked well. I'll respond here later when it's really there.

Steve

Steve - Intel Developer Support

Ok - problem fixed - file is there now. Enjoy!

Steve

Steve - Intel Developer Support

When compiling a free form (.f90) source file that uses tabs, I get the following warning message:
Warning: Extension to FORTRAN-90: tab formatting

Is this supposed to be a warning condition? The documentation would not lead me to believe so.
Is there a work around for suppressing this specific message? The other occasional warnings are lost in a sea of the tab formatting warnings.

Thanks for your consideration

If you ask for Fortran 90 standards checking, then a tab character in the source IS an extension, though the message it is giving is not the one I would have chosen. A tab in the statement part, not part of a comment or character literal, IS an extension.

If you don't like it, turn off standards checking or don't use tabs.

Steve

Steve - Intel Developer Support

OK, I got it. First time the earliest version of the Alpha downlaod didn't do anything funny. Looks like you fixed more instances of unnecessary copies of contiguous arrays; copytest1.f90 runs a little better than 5 orders of magnitude faster now. Still misses cases where an array section with bounds unknown at compile time is passed or when a pointer component of a structure is passed. Still doesn't optimize tensor contractions to anywhere near the extent I would have liked (scheme.f90). Sad that you didn't get it to optimize right logical shifts (perftest.f90).

 
"And now that it's all over 
All I can do is wish you well." 
              - B. B. King 

James,

The shift optimization you suggested has been added to the next "generation" of our code generator, but as you know, it won't be seen on Alpha NT. We've JUST finished work on eliminating unnecessary copies of derived type components and some more cases, though we know of a few others not done yet. Your suggestions and examples have been very helpful - we appreciate your taking the time to send them to us.

Steve

Steve - Intel Developer Support

Steve,
I haven't seen any posting about what is in the 6.5A update.
I would like to know what is in the update before updating.
Thanks,
David

It's primarily bug fixes, with some performance improvements (especially for Athlon). If you have the Professional Edition, the COM Server Wizard can now create EXE servers. Here's the gist of it from the release notes:

  • The Fortran COM Server now allows you to select an out-of-process
    (.EXE) COM server. Users now have a choice of the type of server:
    either a DLL (in-process) COM server or an EXE (out-of-process) COM
    server.
  • New compiler options and their descriptions:
    • /assume:[no]protect_constants
      This option specifies whether
      constant actual arguments can be changed. By default, actual arguments
      that are constants are read-only (/assume:protect_constants). To allow
      changes to actual arguments that are constants, specify
      /assume:noprotect_constants.
    • /check:[no]arg_temp_created
      Requests that a run-time
      informational message appear if actual arguments are copied into
      temporary storage before routine calls. Specifying
      /check:noarg_temp_created (the default) does not generate the extra
      code needed to display a message run-time when this condition occurs.
    • /warn:[no]ignore_loc
      Requests that the compiler issues
      warnings when %LOC is stripped from an argument. The default is
      /warn:noignore_loc (does not issue a warning for this condition).

  • The hardware selected by the /ARCH command line option is the basis
    for the /TUNE option, i.e., you cannot use /TUNE to tune generated code
    for an architecture older than the one selected by /ARCH.
  • New data ATTRIBUTES directive keywords are now available:

    ALLOW_NULL, DECORATE, IGNORE_LOC, and NOMIXED_STR_LEN_ARG

I'll get the release notes up on the web site soon.

Steve

Steve - Intel Developer Support

Leave a Comment

Please sign in to add a comment. Not a member? Join today