Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
5201 Discussions

OneAPI 2025.0 Vtune modulefiles issue?

Tore
Novice
415 Views

Hi,

 

   Seem to be a problem with modulefiles-setup.sh script. Loaded compiler and prereq's as well as vtune.

  Executing icx-cl -fsycl-help fail to locate ocloc and opencl-aot. Loading intel/oneapi/2025.0/vtune/latest sets up an environment which do not include path to vtune.

 

The error:

torel@login1:~$ icx-cl -fsycl-help
Intel(R) oneAPI DPC++/C++ Compiler for applications running on Intel(R) 64, Version 2025.0.4 Build 20241205
Copyright (C) 1985-2024 Intel Corporation. All rights reserved.

Emitting help information for ocloc
Use triple of 'spir64_gen-unknown-unknown' to enable ahead of time compilation
icx-cl: error: unable to execute command: ocloc
Emitting help information for aoc
Use triple of 'spir64_fpga-unknown-unknown' to enable ahead of time compilation
icx-cl: error: unable to execute command: aoc
Emitting help information for opencl-aot
Use triple of 'spir64_x86_64-unknown-unknown' to enable ahead of time compilation
OVERVIEW: OpenCL ahead-of-time (AOT) compilation tool
USAGE: opencl-aot [options] <input SPIR-V or OpenCL program binary>

OPTIONS:

--verbose - Show verbose logs

</snip>

 

The modulefiles for vtune seems culprit.  The prepend-path destination is and environment is not correct. However there is a file in vtune/2025.0/etc/modulefiles/vtune/2025.0 which probably is the correct one.

torel@login1:~$ module show intel/oneapi/2025.0/vtune/2025.0
-------------------------------------------------------------------
/cm/shared/modulefiles/intel/oneapi/2025.0/vtune/2025.0:

module-whatis {Intel(R) VTune(TM) Profiler 2025.0.1}
prepend-path PATH /cm/shared/apps/intel/oneapi/2025.0/vtune/2025.0/etc/modulefiles/bin64
setenv VTUNE_PROFILER_2025_DIR /cm/shared/apps/intel/oneapi/2025.0/vtune/2025.0/etc/modulefiles
setenv VTUNE_PROFILER_DIR /cm/shared/apps/intel/oneapi/2025.0/vtune/2025.0/etc/modulefiles
-------------------------------------------------------------------


torel@login1:~$ ll /cm/shared/apps/intel/oneapi/2025.0/vtune/2025.0/etc/modulefiles/bin64
ls: cannot access '/cm/shared/apps/intel/oneapi/2025.0/vtune/2025.0/etc/modulefiles/bin64': No such file or directory

 

I found binaries icx-cl is complaining about in:

torel@login1:/cm/shared/apps/intel/oneapi/2025.0$ du -a . | grep ocloc
89196 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc/Bin/intel64/libigc.so
2008 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc/Bin/intel64/libigdfcl.so
1460 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc/Bin/intel64/libocloc.so
139056 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc/Bin/intel64/libopencl-clang.so
8 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc/Bin/intel64/ocloc
231728 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc/Bin/intel64
231728 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc/Bin
231728 ./vtune/2025.0/bin64/gma/GTPin/Profilers/ocloc

torel@login1:/cm/shared/apps/intel/oneapi/2025.0$ du -a . | grep opencl-aot
0 ./2025.0/bin/opencl-aot
1136 ./compiler/2025.0/bin/opencl-aot
torel@login1:/cm/shared/apps/intel/oneapi/2025.0$ du -a . | grep aot
0 ./2025.0/bin/opencl-aot
1136 ./compiler/2025.0/bin/opencl-aot

 

Would it seem that nonstandard installations are not handled very well? 

Or am I doing something wrong? 

      

Rgds,
Tore

0 Kudos
3 Replies
Deeksha_S_Intel
Moderator
364 Views

Hi Tore, we would like to inform you that we are routing your query to the engineering team for further assistance.


Tore
Novice
351 Views

Thank you!

In previous versions, because the relative location of module files was different from the installation path, I had to modify the module files, as shown below. However, this has been removed in release 2025.0. Now it only are warned with prereqs.

 

Why? Bug or feature? 

 

<snip>

# Load dependencies
#if { ![ is-loaded tbb ] } { module load tbb }
if { ![ is-loaded intel/oneapi/2023.1/tbb/latest ] } { module load intel/oneapi/2023.1/tbb/latest
}
#if { ![ is-loaded compiler-rt ] } { module load compiler-rt }
if { ![ is-loaded intel/oneapi/2023.1/compiler-rt/latest ] } { module load intel/oneapi/2023.1/compiler-rt
/latest }

# Load optional dependencies (if lmod else tcl)
# see: https://github.com/TACC/Lmod/issues/505
if { [ info exists ::env(LMOD_VERSION_MAJOR) ] } {
# if { ![ is-loaded oclfpga ] } { module try-add oclfpga }
if { ![ is-loaded intel/oneapi/2023.1/oclfpga/latest ] } { module try-add intel/oneapi/2023.1/oclfpga
/latest }
} else {
# get original name of the modulefiles containing folder
set modulefolderroot "[file dirname "$ModulesCurrentModulefile"]"
set modulefolderroot "[file dirname "$modulefolderroot"]"
# if { ![ is-loaded oclfpga ] && [ file exists $modulefolderroot/oclfpga ] } { module load oclfpga }
if { ![ is-loaded intel/oneapi/2023.1/oclfpga ] && [ file exists $modulefolderroot/oclfpga ] } { modul
e load intel/oneapi/2023.1/oclfpga }
}

</snip>

0 Kudos
yuzhang3_intel
Moderator
289 Views

The module file issue on VTune has been fixed. Did you try 2025.0.1?

0 Kudos
Reply