Anomalies after converting CVF to IVF

[mike_desylva]

I am working on making some minor modifications to a very large simulation program (written by multiple other programmers) that works under CVF. I have ported it to IVF and gotten it to compile again, but I am now getting a lot of anomalies.

I followed the porting instructions and have gone through all the Project properties look for settings that could be causing the problems, but haven't had any luck.

I also attempted to do the conversion again on a different computer, but ended up with the same problems.

I have stepped through the debugger attempting to correct the problems, but I just keep coming upon other ones.

An example of a line of code not working properly is:

GO TO (1000, 2000, 3000), index

When it hits that statement itjumps to the end of the subroutine and never goes to 1000, 2000, or 3000, regardless of the index number.

I replaced it with three IF GO TOs to get past that, but then I get other similar problems.

I am wondering if there may be something I did to cause these problems or if these kinds of problems are normal.

Somebody told me it was safer to rebuild the project again from scratch rather than converting it to avoid those problems.

After all that, my question is:

Should I rebuild from scratch? It is a HUGE project and I would like to avoid it. Are there any other ideas on why I would have problems like that?

I don't currently have CVF, but I am considering buying it too to get past this. Debugging is just taking too long to make it work and there has to be a better way.

Thanksa lot.

Mike

[Steven_L_Intel1]

Those symptoms do sound strange. I suggest you send a copy of your program to Intel Support along with instructions for reproducing the problem. It seems as if you've done your part so far. My guess is that you're corrupting the stack somehow...

[Steven_L_Intel1]

I'm not sure what you mean by "rebuild from scratch". Certainly, you do need to recompile all the code in the project. If they gave you a CVF project and you "converted" it to the new format, I suggest trying this. Right click on the project, select Properties, Fortran, External Procedures. Change the calling convention and string argument passing to default (a CVF-converted project will have CVF settings here.) Then rebuild the "solution".

If this doesn't help, send a ZIP file of your solution folder, with sources, to Intel Support and provide instructions for reproducing the problem. We'll be glad to take a look. There should be no need for you to buy CVF.

[mike_desylva]

Steve,

By rebuild from scratch, I meant not use the CVF projects at all, but instead,create anew solution and all new projects in IVF using just the source files the CVF project was based on. I am not sure if or how that would help me, but it was suggested.

Basically, what I did was take the original CVF project/solution, deleted the .ndb files, opened it in IVF, let it convert all to the C++ format, then extracted the IVF projects. I then attempted to rebuild everything. I ran into a few compilation problems that were solved by changing the calling conventionfrom CVF to default. I have triedusing several different property settings, but I have not found acombination that produces good results. It compiles fine, but the results are bogus due to problems like the GO TO described in my first question.

The program is very large and it is classified, so I cannot send it in.

I was just hoping I could get some ideas as to whether it would be worth the substantial effort for me to make the project from scratch using the source files or not, and whether there might be some other property settings that could cause problems like that.

Thanks again for your help. I know it is tough to do much of anything without me being able to send my code to Intel.

Mike

[Steven_L_Intel1]

I see. Well, try the suggestion I made above about changing the calling convention. But really, it isn't hard to create a new project and then add the existing source files.