Development Tools

Problems with Top-down Microarchitecture Analysis Method

I'm trying to analyse an execution on an Intel IvyBridge CPU (Xeon E5-2620 V2) with the Top-down Microarchitecture Analysis Method, described in Chapters B of the Intel® 64 and IA-32 Architectures Optimization Reference Manual.

Therefore I perform performance counter events measurements with Perf (perf stat -e rNNN), There are some results I don’t understand:



I'm supporting a legacy fortran program. Everything runs fine except for a few clients who get the following message:

cannot open message catalogus "\1043\libguide40ui.dll"

I'm not new to programming, but rather new to fortran and read something about this library on this forum, but I don't understand what I should do to get rid op the issue as easy as possible. Should copying libguide40ui.dll to the program directory solve the problem, and is that a good solution ?

If no ... what should I do (simple step by step explanation would be welcome)


recursive subroutines and stack size

I am experimenting with recursive subroutines.  If I compile and run a simple program, where a recursive subroutine calls itself many times, it crashes with a stack overflow.  I have figured out that to fix this, I have to set the Stack Reserve Size to a large value.  Is there a way to disable the stack usage?  I have tried using /heap-arrays0 option, but it did not help.

If I can't disable the stack and I want to use recursive subroutines, do you think I should just set the Stack Reserve Size to a maximum of 1 GB to prevent any stack overflows?


Translating Visual Studio project to command line

For various reasons, I need to use the compiler at command line to compile a project that I had previously been compiling successfully in Visual Studio 2012. 

The Solution properties pages show several different command lines, one for "Fortran," one for "Linker," one for "Resources," and one for MIDL. Can I combine these somehow as as argument to the ifort command so that one call to ifort builds the entire solution (equivalent to "Rebuild Solution" in Visual Studio)? If so, how? Just concatenate them, or something else?

DLL Considerations

I have two DLLs that I'm interested in.  Let's call them Main.dll and Plugin.dll, both written in Fortran.

Plugin.dll needs to access various functions and COMMONs from Main.dll.  Ok, so I added a few


kind of statements, and created a module definition file to go along with Main.dll.  The user of Main.dll and Plugin.dll loads everything into memory, and life is good.

Couple of silly Linux-related bugs


I bumped into two silly bugs in the Linux version of VTune while analyzing performance of my application. I managed to workaround both bugs, so no help needed. I just would like to make a bug report. If this forum is not the right place to do this, please point me in the right direction.

1) fails if path to installation files contains space characters, e.g.:

Subscribe to Development Tools