Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Built my first IVF 8 program...

lklawrie1
Beginner
1,618 Views
That is I built the version of the software we are running on CVF. Debug version on IVF is 60MB!!!! On CVF, it's only about 10MB. What options did I pick incorrectly?
Another problem: tried to register the software using my id (lklawrie) and password that I've had since May 2003. The registration process says the id or password are invalid but if I try for a new account under my email -- says I am already a user...
And another difference for IVF...
It doesn't like:
If (found /= 0 .and. array(found)...) then
when found=0 -- a bomb on the array bounds of 0 for array.
Linda
0 Kudos
7 Replies
Steven_L_Intel1
Employee
1,618 Views
If you're having a problem with the registration center, please describe the problem in an e-mail to [email protected]
I can't comment on the image size without seeing an example and knowing what options you used.
Your compound IF could have failed on CVF too - it makes an invalid assumption about the order of evaluation of operands in a logical expression.
0 Kudos
lklawrie1
Beginner
1,618 Views
Actually getting very confusing results...
The image size of the debug version (IVF) is 60MB. When I compiled "release" version (IVF) it's 5.5MB.
I got the pointer to the compound If from taking the exe and putting it on a different system (where I have all the input files) and looking at the traceback from the results.
In the debugger (back on the system that has the IVF compiler, etc), it flies past that statement (apparently processing it correctly) but it is bombing in the debugger in an "output.c" routine that I have stepped wise through the code and it appears to be crashing on a TRANSPOSE statement.
Does that make any sense? The output.c routine (with my somewhat limited knowledge of c) seems to be outputting a string.
If I can pare down this particular problem, I may be able to submit it to the compiler developers/debuggers. So far, it's quite puzzling.
(And will go to the registration email you suggested).
Thanks.
Linda
0 Kudos
Steven_L_Intel1
Employee
1,618 Views
Linda,
I would encourage you to submit to Intel Premier Support an example of the program which you think executes incorrectly. Please do spend a few minutes first trying to see if you can work out what is wrong first, though.
I can believe that optimization would reduce EXE size.
0 Kudos
lklawrie1
Beginner
1,618 Views

Probably what I need to do first is get a more comparable set of "fortran options" between the IVF debug/release and CVF debug/release. I accepted the IVF defaults which may be more stringent than CVF.

Right now -- the command line for the debug version does different stuff, though, from the "window debugger". And the release version command line is different from the debug command line. (This is a console application).

Can't spend vast amounts of time, though, so was trying for something expedient.

Linda

0 Kudos
Steven_L_Intel1
Employee
1,618 Views
The defaults when compiling in the IDE are very different from compiling on the command line - especially in debug configuration. Release configuration is not so different. This is just as it was with CVF.
0 Kudos
lklawrie1
Beginner
1,618 Views
Compiling from the command line is not high on my list of preferred activities. What I mean was compiling from within the IDE and stepwise through the code vs. compiliing from within the IDE and then using that compiled exe from the command prompt.
I think I now have all 3 versions (IDE-stepwise debug, IDE-command prompt exe (debug) and IDE-command prompt (release)) all stopping on the Transpose line -- at least that's what the traceback tells me. According to the debug, it's somewhere in a system dll.
As I have time, I will try to zip up a small (as it can be) set of source, project workspace, etc to send to technical support.
Linda
0 Kudos
Steven_L_Intel1
Employee
1,618 Views
Please do send an example to support. I can't get a good sense from your description as to what the problkem is - the "system DLL" isn't really relevant - that just happened to be active while your program runs.
0 Kudos
Reply