Intel® Visual Fortran Compiler for Windows | Forum profile

No, you don't have to link anything.  Try running the repair tool linked here . -------- Steve Attaching or including files in a post Doctor Fortran blog @DoctorFortran on Twitter

stack overflow is likely to be fixed by the standard /link /stack:nnnnnnnnn described in your CVF help. I've become rusty on the CVF facilities for checking syntax errors, but it looks like you should be turning all of them on (subscript range check, uninitialized variables, consistent CALL arguments). When people say "fortran 77" they often mean lots of non-standard stuff, not f77, but CVF does support the most usual...

Quoting - Steve Lionel (Intel) No, it is not the processor (or at least that would be the last thing I would suspect).  What is the exact nature of the problem? The compiler options I am using are the following /nologo /O3 /Og /Qipo /free /Qopenmp-report0 /Qpar-report0 /Qvec-report0 /warn:declarations /warn:unused /warn:ignore_loc /warn:truncated_source /warn:interfaces /real_size:64 /module:"Release/" /object:"Release/"...

I considered this option however the program runs iterations in the region of 10^(12) or more in some cases. This seems like a really large data which is why im now considering only storing the previous three.  

Quoting - tim18 Normally, you would not use a Fortran main as well as a C++ main.  Your C++ would call a Fortran procedure set up with iso_c_binding (although that came years later than your C++) or equivalent Windows-specific interfacing. Hi tim, actually the code is in 'C' language and i just renamed the file names to .cpp. Is there any settings option that I need to set as iso_c_binding to run as c main? Because when i am...

Thanks for attention!

Quoting - Steve Lionel (Intel) I didn't have trouble with CVF on Vista, once I learned to run DevStudio "as administrator".  CVF installs on Windows 7 x64 but won't run. Yeath. Sometimes it worked fine for me without change. But it was not the always case.  I also find there are others in my condition, so I paste my method.  

Quoting - Steve Lionel (Intel) Probably the simplest solution is to add /MT (Multithread static library) to your Fortran command (fl32).  Make sure that your C compile also specifies this.  /MD (multithread DLL) is an alternative. Many thanks Steve, that has fixed those build problems ( /MD was what I needed). I have a couple of other issues which I think are unrelated and then we get to see what happens when I run it ;-)

Hi, this is a follow up on the previous thread because I still don't see the solution: 1) I use Intel Visual Fortran Compiler v11.1 2) I have installed Array Visualizer v3.3 Currently, on right click of an array I wish to display I cannot select the "View Array" Option. So I guess I have to link the Compiler with the Visualizer. But... How do I link the Compiler with the Visualizer, i.e., how do I add the path? Would this be...

Dear Fortran friends, I try to get my program to work with "11.1 build 51" as it did in "11.0.072" and a few earlier compilers. In one thread I use -- WriteConsoleInput() -- to write to the console, while another thread wait in a -- READ(i,20,END=10)strtmp 20 FORMAT(A) -- to receive the command as a text string. This used to work well... but then I try with 11.1 and there the fun ends. Prior to 11.1 the READ exits when...