Community
cancel
Showing results for 
Search instead for 
Did you mean: 
TimP
Black Belt
31 Views

KNL link line for itt_pause(), itt_resume()

The following link line fails to resolve references to __ittpause and __itt_resume:

mpiicc -std=c99 -debug inline-debug-info -O3 -xMIC-AVX512 -fPIC -fno-alias -ansi
_alias -fp-model fast=2 -qopenmp -mkl -qopt-report=4 -restrict -I/opt/intel/2017
/vtune_amplifier_xe_2017.0.2.478468/include -L/opt/intel/2017/vtune_amplifier_xe
_2017.0.2.478468/lib64/  -o inviscid_rk inviscid_v3_deleaved_c.o main.o  -littno
tify

 

Does it mean there is no support for these old VTune API functions here?

I don't know the sysadmin on this remote system so don't know exactly how things were installed there.

The task at hand is to determine whether OpenMP functions are spending much time in a specific omp for loop in a parallel region which scales well with problem size but runs slowly with a problem size which keeps about 32 threads out of the 64 busy.  The original code timed the loop by restricting the timer to thread ID 0.  I suspect #omp pragma restrict (or maybe master) may give more meaningful timing; something seems strange about the timing where there isn't sufficient work to keep all threads active.  Still there seems to be too much time spent there, and -collect hpc-performance reports high serial time overall.

I could imagine that some more modern features of VTune might be more suitable, but I don't find enough detail in documentation.

 

0 Kudos
0 Replies