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

Profiler for Fortran (ifort) with function call count

Limon
Novice
1,267 Views

Hello dear experts

Just upgraded to OneAPI + Fortran from the old Composer XE 2013 and need to perform some profiling. (Visual Studio 2022, Windows)

 

VTune Profiler detects hotspots and shows the time percentage for every function.

However, it does not show the Function call count, only the time percentage:

Limon_0-1652210440095.png

 

The time spent in the function is not very informative without knowing how many times this function was called.

In the old 2013 Intel Fortran we had this compiler option:
/Qprofile-functions:all

and it generated a nice report about ALL function call counts, time, loops etc.

Now the new ifort help does not show this option.

When trying to compile with it says:
ifort: command line warning #10157: ignoring option '/Qprofile-loops'; argument is of wrong type

 

Wondering what is the way now to get the function call counts.

Thanks.

Ivan.

Labels (1)
0 Kudos
1 Solution
Ron_Green
Moderator
1,215 Views

the Advisor tool has call counts.  Scroll down THIS THREAD to the 2nd to the last post.  It also drills down to loop-level for hot loops, trip counts.  I find it more user friendly than Vtune, which is designed for micro-architecture details (too low level for me).

 

View solution in original post

4 Replies
Ron_Green
Moderator
1,216 Views

the Advisor tool has call counts.  Scroll down THIS THREAD to the 2nd to the last post.  It also drills down to loop-level for hot loops, trip counts.  I find it more user friendly than Vtune, which is designed for micro-architecture details (too low level for me).

 

Limon
Novice
1,188 Views

Thanks for the reply!
It truly works!

 

Do you know by any chance why i need to check "FLOP", otherwise function call count won't show up? I thought FLOP is floating-point operations. Looks irrelevant for function call count, but it works...

0 Kudos
Ron_Green
Moderator
1,175 Views

the Advisor team put it as part of Flop counts.  They didn't want yet another collection type.  Too confusing when there are too many collection options - look at Vtune for example.    Their thinking was the FLOP collection is already doing deep profiling so adding function call counts was super easy to do at the same time.

 

0 Kudos
Limon
Novice
1,167 Views

Make sense, appreciate your help!

0 Kudos
Reply