Re: Latest Patch .048, some mod files out of date?

ipattielgc · ‎04-28-2004

First, thanks to Intel for releasing the .048 patch, it fixed my "iface:cvf" bugs related to function decoration of routines with character arguments.

However, it seems like some of the mod files in the Include directory are now out of sync. In particular, I had to re-compiler ifcom.f90 to link to:

INTEGER*4 FUNCTION ConvertStringToBSTR(string)
USE OLEAUT32
USE IFNLS
CHARACTER*(*), INTENT(IN) :: string

which I guess was complied with .047. I'll report this to Premier Support, meanwhile re-compiling this module fileis the workaround.

FWIW, after applying the .048 patch, the mod file date is 4/12/2004, 12:18 PM.

-Ian

Jugoslav_Dujic · ‎04-28-2004

...in addition, the premier web page seems to be prepared in a hurry:

Intel Fortran Compiler for Windows*
Intel C++ Compiler for Linux v8.0 IA32 Update patch is available for download. Build Information: IA32 Compiler Build 20040415 Package ID: W_CC_PC_8.0.047_PE048.1 (W_FC_PC_8.0.047_PE048.1.exe)

The above paragraph contains some contradictions, isn't it? Apparently, i'm not the only one who overuses copy/paste ;-).

Jugoslav

ipattielgc · ‎04-28-2004

Yes, that took a bit of staring at. Meanwhile, the simple console app I made to send to Premier Support does not seem to demonstrate my problem from the first post. I will have to investigate more before I formally report it. Ian.

Steven_L_Intel1 · ‎04-28-2004

Ian,

I don't understand the problem you describe. I tried a simple example and it worked. What was the symptom of the problem you encountered?

Jugoslav, I've let the appropriate people know about the incorrect web page.

Aren't you folks at all happy that we're providing patches instead of full replacement kits? :-)

Jugoslav_Dujic · ‎04-28-2004

Aren't you folks at all happy that we're providing patches instead of full replacement kits? :-)

We are, but isn't the definition of user "the one that complains"? :-).

On the same line, 48 MB patch, eh...

Jugoslav

ipattielgc · ‎04-28-2004

Steve

The trick is to pretend you've just converted a CVF project to IVF (and who wouldn't!), so the the calling convention is:

"iface:cvf"

then try this simple program:

program
Console1
use ifcom
implicit none
integer :: bstr1
character(len=16) :: cvar
cvar='Something'
bstr1 = ConvertStringToBSTR(cvar)
end program Console1

it will not build. Funny thing is, yesterday (.047) it would!

A dumpbin of ifcom.lib shows that the trailing "@8" is missing from "ConvertStringToBSTR". This is probably an Interface issue with an include file to override compiling calling conventions so these things always work. I'm still poking around... Thanks, Ian.

Steven_L_Intel1 · ‎04-28-2004

Yeah, but that's a lot smaller than the full kit. The way we're doing patches is to replace the files that have changed. Due to the frequency that Intel does compiler updates, doing binary edits the way CVF did would be prohibitively expensive for us in terms of testing, due to the nature of "history patching". Furthermore, you no longer have to uninstall and reinstall, which is a big win.

The size of the patch ought not to change much over time, and of course it's your option whether to get every update.

Jugoslav_Dujic · ‎04-28-2004

I understand (and assumed so)Steve, I was kidding. It's definitely better to have frequent updates like with Intel.

Still, I applied .048 patch over .044installation and it didn't complain (I had decided not to install .047 just because of Ian's problems.). Is it safe, or should I have installed 047 first? It's not clear to me how Intel can manage to upgrade version .whatever to the current one (except if every patch replaces just the "dynamic" part, which means that every future one will be approx. 50 MB).

Jugoslav

ipattielgc · ‎04-28-2004

Steve

The patch methodwas ok. I tried it as a full install first (no previous IVF), and it failed (as expected), but there was no message saying "first install the full version", it just failed. I installed .047, then all was well.

On the other subject, I tracked down the problem, and I think its as simple as the fact that:

ifcom.f90 is missing 2 interfaces, for:

ConvertStringToBSTR and ConvertBSTRToString

which are needed to support all the combos of calling conventions you poor guys have committed to!

Things are looking pretty good. Thanks, Ian.

g_f_thomas · ‎04-28-2004

Patches are an improvement.

I installed IVF Pro on Monday directly from Intel. The IDE 'about' reads:

Intel Fortran Compiler Integration for Microsoft Visual Studio .NET 2003, Version 8.0.2149.2003

How is 8.0.2149.2003 related to patch 0.048?

Thanks,
Gerry T.

Steven_L_Intel1 · ‎04-28-2004

It isn't - not directly, anyway. The 048 is a kit identifier. The Fortran kit contains numerous components, each with their own internal identification. Sometimes support will ask you for the internal ident strings. When the components are built, we don't know what the kit will be numbered.

g_f_thomas · ‎04-28-2004

The patch site states:

"The package id is W_FC_PC_8.0.047_PE048.1. IA32 Compiler Build 20040415. The baseline package ID is W_FC_PC_8.0.047. Please download the readme file and CompilerPatchHowToWin.txt for important installation instructions. You must apply this patch to the W_FC_PC_8.0.047 package."

It would appear that the patches are not cummulative. So is the Intel Fortran Compiler Integration for Microsoft Visual Studio .NET 2003, Version 8.0.2149.2003 installed a couple of days ago as current as W_FC_PC_8.0.047 or do I have to uninstall IVF 8.0.2149.2003, install W_FC_PC_8.0.047, and then apply W_FC_PC_8.0.047_PE048.1?

Ciao,
Gerry T.

Steven_L_Intel1 · ‎04-28-2004

There is no such thing as " IVF 8.0.2149.2003". That is the version of the IDE integration component of IVF that is specific to VS.NET 2003. Patches are cumulative and you can skip intermediate versions back to the identified "base" version, which in this case is 8.0.047. At some point in the future - probably whena new release comes out, - we will "reset the baseline" so that future patches need to be applied on top of the new version.

As long as you start with 8.0.047, you simply install the patch and it takes care of everything. I don't know if the IDE integration changed in this patch, but if it did, then that would be included.

g_f_thomas · ‎04-28-2004

It turns out that the version of IVF Pro on the Intel site is w_fcp_p_8.0.048.exe which would seem to imply that the .048 patch has already been applied. FYI, the FSupport.text supplied in the NOTES folder claims that the package id for w_fcp_p_8.0.048.exe is w_fc_pc_8.0.047.

HTH,
Gerry T.

Steven_L_Intel1 · ‎04-28-2004

Sigh. I know this is confusing..

The compiler in the Pro kit is 047. For packaging reasons, the Pro kit got a new number, but the compiler part of the package IS the 047 kit. But that doesn't explain why they picked 048 for the patch - I would have expected 049. Oh well...

eddie_breeveld · ‎04-30-2004

I'm very happy it's a patch, not a full release. It doesn't touch my IDE toolbars, it's a lot smaller to download, andit doesn't effect my environment variables! There may be a few other plusses too.

All the best,

Jugoslav_Dujic · ‎04-30-2004

But there's no .047 full kit (IA32) on the Premier web page anymore! The latest full version available is .042. That means that, if someone didn't upgrade timely to 047, he won't have any "base" to start from (unless .042 can serve?). As for myself, I haven't downloaded .047 (dut to above-mentioned problems) and I feel a bit uneasy because Iapplied the patch to installed .044.

Any chance that the kit ID (the three-digit notation as used above) is built-in into compiler so that less confusions occur? The compiler now identifies itself as

Intel Fortran Compiler for 32-bit applications, Version 8.0 Build 20040415Z

but it's a bitinconvenient to refer to it as "20040415Z". Also,a bit odd is that neither of core .exe files in Bin folder has Version Info resource built-in.

Jugoslav

Steven_L_Intel1 · ‎04-30-2004

I still see the full 8.0.047 kit on Premier Support.

The three digit number is there in the next line you didn't include. For example:

Intel Fortran Compiler for 32-bit applications, Version 8.0 Build 20040415Z
Package ID: w_fc_pc_8.0.047_pe048.1

Jugoslav_Dujic · ‎04-30-2004

I still see the full 8.0.047 kit on Premier Support.

Hmm, trust me, I don't. I'm looking at https://premier.intel.com/WhatsNew.aspx, filtered by "Intel Fortran Compiler for Windows". First 4 items are dated 4/27/2004 (048 update), 5th is f90GL update, 6-9 are dated 2/24/2004, related with 042 full kit.

The three digit number is there in the next line you didn't include.

Sorry for being dense, there's no next line. I typed just "ifort" on command line -- is there some additional switch I forgot?

Jugoslav

Steven_L_Intel1 · ‎04-30-2004

Try "File Downloads" instead of "What's New". I don't know how the "What's New" is filtered.

Here's what I get when I type ifort:

ifort: Command line error: no files specified; for help type "ifort -help"

What do you see?

ipattielgc · ‎04-30-2004

Steve, yes, but what you see and posted is the "patch". The .047 full is gone. I also had to go find an old backup to install it before applying the patch. Ian.