Visible to Intel only — GUID: GUID-2041F107-7761-4DED-8EE2-CD8F2C053BEA
Why is FPGA Compilation Different?
Types of SYCL* FPGA Compilation
FPGA Compilation Flags
Emulate and Debug Your Design
Evaluate Your Kernel Through Simulation
Device Selectors for FPGA
FPGA IP Authoring Flow
Fast Recompile for FPGA
Generate Multiple FPGA Images (Linux only)
FPGA BSPs and Boards
Targeting Multiple Homogeneous FPGA Devices
Targeting Multiple Platforms
FPGA-CPU Interaction
FPGA Performance Optimization
Use of RTL Libraries for FPGA
Use SYCL Shared Library With Third-Party Applications
FPGA Workflows in IDEs
Intel oneAPI DPC++ Library (oneDPL)
Intel oneAPI Math Kernel Library (oneMKL)
Intel oneAPI Threading Building Blocks (oneTBB)
Intel oneAPI Data Analytics Library (oneDAL)
Intel oneAPI Collective Communications Library (oneCCL)
Intel oneAPI Deep Neural Network Library (oneDNN)
Intel oneAPI Video Processing Library (oneVPL)
Other Libraries
Visible to Intel only — GUID: GUID-2041F107-7761-4DED-8EE2-CD8F2C053BEA
Memory-Mapped interfaces
You can instantiate Memory-mapped (MM) interfaces in one of the following ways:
Memory-Mapped Interface Using Accessors: Using accesors allows the compiler to manage the copying of the memory between the host and device.
Memory-Mapped Interface Using Unified Shared Memory: Using unified shared memory (USM) lets you take full control and manage copying data from the host to the device and vice versa. However, USM pointers allow you to customize the memory-mapped host interface further.