View page
Talk page

Intel oneAPI

This page can't be edited. | Page History
    Table of contents
    You are currently comparing two old versions - only when you are comparing against the latest version can you revert. Return to version archive.

    Combined revision comparison

    Comparing version 16:19, 5 Jan 2022 by jwagner with version 16:28, 5 Jan 2022 by jwagner.

    Installed oneAPI Base toolkit and oneAPI HPC toolkit on 9/2021 for test purposes. Installed on compute nodes, head nodes, Mark6'es.

    ...

     For additional info from Intel see https://www.intel.com/content/www/us/en/developer/tools/oneapi/toolkits.html

    The installation under /opt/intel/oneapi/ provides its own Intel IPP, Intel MPI Library, Trace Analyzer and Collector, Intel VTune Profiler, and Intel compilers (CC: icc, CXX: icpc).

    Environment

    Activate with:

    source /opt/intel/oneapi/setvars.sh

    For DiFX, the usual setup_difx script(s) should have:

    #!/bin/bash

# Get oneAPI environment
# Prepares IPPROOT, CMPLR_ROOT, I_MPI_ROOT, ...
if [[ "$I_MPI_ROOT" == "" ]]; then
        . /opt/intel/oneapi/setvars.sh
fi
if [[ "$IPPROOT" == "" ]]; then
        export IPPROOT=$ONEAPI_ROOT/lib/intel64/
fi

# Add Intel-libs path in case the current host has only the runtimes but not entire devel toolkit
installed; the automatic setvars.sh does not appear to cover that case...
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/intel/oneapi/lib/intel64/

# Intel MPI
export OPENMPIROOT=$I_MPI_ROOT

# Intel Compilers
# Note on icc, vs icpc, vs icx, vs icpx, vs icl: 
#  https://software.intel.com/content/www/us/en/develop/articles/porting-guide-for-icc-users-to-dpcpp-or-icx.html
export CC=icc
export CXX=icpc
export MPIXCC=${OPENMPIROOT}/bin/mpicxx
export MPICXX=${OPENMPIROOT}/bin/mpicxx

    Version from 16:19, 5 Jan 2022

    This revision modified by jwagner (Ban)

    ...

    Version as of 16:28, 5 Jan 2022

    This revision modified by jwagner (Ban)

    Installed oneAPI Base toolkit and oneAPI HPC toolkit on 9/2021 for test purposes. Installed on compute nodes, head nodes, Mark6'es.

    ...

    For additional info from Intel see https://www.intel.com/content/www/us/en/developer/tools/oneapi/toolkits.html

    The installation under /opt/intel/oneapi/ provides its own Intel IPP, Intel MPI Library, Trace Analyzer and Collector, Intel VTune Profiler, and Intel compilers (CC: icc, CXX: icpc).

    Environment

    Activate with:

    source /opt/intel/oneapi/setvars.sh

    For DiFX, the usual setup_difx script(s) should have:

    #!/bin/bash

# Get oneAPI environment
# Prepares IPPROOT, CMPLR_ROOT, I_MPI_ROOT, ...
if [[ "$I_MPI_ROOT" == "" ]]; then
        . /opt/intel/oneapi/setvars.sh
fi
if [[ "$IPPROOT" == "" ]]; then
        export IPPROOT=$ONEAPI_ROOT/lib/intel64/
fi

# Add Intel-libs path in case the current host has only the runtimes but not entire devel toolkit
installed; the automatic setvars.sh does not appear to cover that case...
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/intel/oneapi/lib/intel64/

# Intel MPI
export OPENMPIROOT=$I_MPI_ROOT

# Intel Compilers
# Note on icc, vs icpc, vs icx, vs icpx, vs icl: 
#  https://software.intel.com/content/www/us/en/develop/articles/porting-guide-for-icc-users-to-dpcpp-or-icx.html
export CC=icc
export CXX=icpc
export MPIXCC=${OPENMPIROOT}/bin/mpicxx
export MPICXX=${OPENMPIROOT}/bin/mpicxx