Skip to content

Latest commit

 

History

History
104 lines (76 loc) · 3.31 KB

environment.rst

File metadata and controls

104 lines (76 loc) · 3.31 KB
Raw

Environment variables with triSYCL

triSYCL currently has one optional environment variable to turn on a work in progress feature. triSYCL also makes use of some libraries that have their own environment variables that can effect the build process.

Of course the generic environment variables of the operating system have impacts on the execution, for example by selecting the right dynamic libraries and so on.

triSYCL Variables

TRISYCL_USE_OPENCL_ND_RANGE

When set to "1" the triSYCL Makefile will add the definition "TRISYCL_USE_OPENCL_ND_RANGE to the appropriate compile steps to allow the execution of parallel_for kernels using OpenCL's ND-range. This should be used in conjunction with the other triSYCL OpenCL environment variables.

Otherwise the kernels are executed as a single task with 1 work-group and 1 work-item only and all the ND-range is actually executed with a loop nest inside the kernel. This is a typical use case for FPGA.

Boost.Compute

In this library https://www.boost.org/doc/libs/release/libs/compute used to support OpenCL, there are some environment variables described in https://github.com/boostorg/compute/blob/master/include/boost/compute/system.hppto that influence the default device used by the implementation:

BOOST_COMPUTE_DEFAULT_DEVICE
name of the compute device (e.g. "GTX TITAN")
BOOST_COMPUTE_DEFAULT_DEVICE_TYPE
type of the compute device (e.g. "GPU" or "CPU")
BOOST_COMPUTE_DEFAULT_PLATFORM
name of the platform (e.g. "NVIDIA CUDA")
BOOST_COMPUTE_DEFAULT_VENDOR
name of the device vendor (e.g. "Xilinx")
BOOST_COMPUTE_DEFAULT_ENFORCE
If this is set to "1", then throw a no_device_found() exception if any of the above environment variables is set, but a matching device was not found.

There are also some macros such as BOOST_COMPUTE_USE_OFFLINE_CACHE than can be used to cache the kernels instead of recompiling them every time.

OpenMP

triSYCL can use OpenMP to speed up execution of the kernels on CPU.

Look at the documentation of the implementation you are using to see the list of environment variables.

For example with GCC libgomp look at https://gcc.gnu.org/onlinedocs/libgomp/Environment-Variables.html describing for example among others:

OMP_NUM_THREADS
Specifies the number of threads to use

OpenCL backend

Refer to the OpenCL implementation you are using for the useful environment variables.

Xilinx Hardware Emulation

triSYCL can be used in conjunction with Xilinx's Software and Hardware Emulation when compiling using SDx and xocc for FPGA's to simulate the results of running the kernels on Xilinx hardware. Two environment variables are used to support this:

XCL_EMULATION_MODE
Defines the emulation mode you wish to compile to either sw_emu or hw_emu. If undefined it will default to hw and look for a real device.
TARGET_DEVICE
Define the platform/device you wish to target. If undefined it will default to xilinx_vcu1525_dynamic_5_1.