Intel® Fortran Compiler

PSXE 2017 Update 2 - Internal Compiler Error(s) involving PARAMETER constants and /debug-parameters /debug options

PSXE 2017 Update 2 - Internal Compiler Error(s) involving PARAMETER constants and /debug-parameters /debug options

A defect (regression) has been found in the Intel® Parallel Studio XE 2017 Update 2 (17.0 compiler) release involving the use of PARAMETER constants along with the /debug-parameter and /debug options. The combined use can led to multiple internal compiler errors.

The following example (complements of andrew_4619) demonstrates usage that will trigger the internal error:

rc.exe not found

I have a piece of code that runs on another computer that I'm trying to compile and run on my computer but whenever I try to build the solution I get an error rc.exe not found. I've done some research and believe that the issue is related to having the wrong combination of Visual Studio and Intel Fortran installed together. I've tried uninstalling and reinstalling several different version of both VS and Parallel Studio, ranging from 2013 - 2017 but I have not had much luck.

Оптимизировали, оптимизировали, да не выоптимизировали!

Оптимизация? Конечно, каждый сталкивался с данной задачей при разработке своих, сколь-нибудь значительных, требующих определённых вычислений, приложений. При этом способов оптимизировать код существует огромное множество, и, как следствие, различных путей сделать это в автоматическом режиме с помощью опций компилятора. Вот здесь и возникает проблема – как выбрать то, что нужно нам и не запутаться?

full screen

I develop QuickWin applications.

When starting, a program gets the x and y pixel numbers through GETWINDOWCONFIG and opens a window through SETVIEWPORT.

The program is dedicated to run in FULL SCREEN, is there a function that can be called by the program to switch to FULL SCREEN ? The only way I found is to manually hit ALT+ENTER.

I use 2 screens, I can move the program's window to the second screen, but when I hit ALT+ENTER, the window comes back automatically to the main screen. Is there a way to have it stay on the second screen ?

in the EDITOR :

F77 and F90

Hello.

Is their a possibility to handle F77 fixed format FORTRAN-files and F90 free format FORTRAN-files with an option automatically or have I insert manually the -free option?

Thanks in Advance.

Regards
Cetin

Very slow editor response in Visual Studio

Hello, I'm getting very slow response in the visual studio editor, key presses can take up to 2 seconds to appear on the screen. My other applications seem to be responding normally. It seemed to get slower with time, so I checked system memory usage for the VS application and it was 310Mb. I restarted VS, did a compile attempt again and memory usage was 150Mb. I know this is not a good description of my problem but I'm hoping someone can kindly point me in the right direction. My system info shown below

best regards

karl skinner

 

How to determine newly assigned variables

I currently use Intel Visual Fortran 2013 with Visual Studio 2012. I am working with a large 3rd party program including dozens of source files with thousands of lines of code. To facilitate understanding/debugging the code, I have two questions:

1) Does there exist a way, while stepping through the code, to determine all NEWLY assigned variables? Currently I use a whole lot of Debug.Print on the command line to determine what such and such variable is. However I would like to determine only the variables updated by the most recent step.

Subscribe to Intel® Fortran Compiler