OpenCL* on Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA Quick Start User Guide

Download PDF
ID 683831
Date 6/05/2020
Public
Document Table of Contents
Document Table of Contents x
1. About this Document 2. Setting Up the Host Machine 3. Running Diagnostics 4. OpenCL* Support for Multi-Card Systems 5. Running Samples 6. Compiling OpenCL* Kernels 7. Intel® PAC with Intel® Arria® 10 GX FPGA Security for OpenCL* Applications 8. OpenCL* on the Intel® PAC with Intel® Arria® 10 GX FPGA Quick Start User Guide Archives 9. Document Revision History for OpenCL* Quick Start User Guide Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA
1. About this Document x
1.1. Conventions 1.2. Acceleration Glossary 1.3. Acronyms
2. Setting Up the Host Machine x
2.1. Introduction 2.2. Initializing the Environment for OpenCL* with Intel Acceleration Stack 2.3. Initializing the Intel® Acceleration Stack for OpenCL* in a Virtualized Environment
2.1. Introduction x
2.1.1. Release Content
5. Running Samples x
5.1. Running Hello World 5.2. Running Vector Add
6. Compiling OpenCL* Kernels x
6.1. Checking Timing Results
1. About this Document
2. Setting Up the Host Machine
3. Running Diagnostics
4. OpenCL* Support for Multi-Card Systems
5. Running Samples
6. Compiling OpenCL* Kernels
7. Intel® PAC with Intel® Arria® 10 GX FPGA Security for OpenCL* Applications
8. OpenCL* on the Intel® PAC with Intel® Arria® 10 GX FPGA Quick Start User Guide Archives
9. Document Revision History for OpenCL* Quick Start User Guide Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA

6.1. Checking Timing Results

Intel® recommends that you check for timing failures after compilation of the kernel file.
Check the compilation directory for the presence of the following report files: 
afu_default.failing_clocks.rpt
afu_default.failing_paths.rpt

For example, after compiling vector_add.cl, locate the $OPAE_PLATFORM_ROOT/opencl/vector_add/bin/vector_add directory. If there is a timing violation, this directory contains the failing report files. The failing report files indicate that the timing is not clean and the functional correctness cannot be guaranteed.

If OpenCL* kernel compilation results in timing violations, Intel® recommends to retry compilation with a different seed (aoc <kernel.cl> -seed=<integer_value> ).

For example, 
aoc device/vector_add.cl -seed=2 -o bin/vector_add.aocx -board pac_s10_dc
aoc device/vector_add.cl -seed=3 -o bin/vector_add.aocx -board pac_s10_dc
aoc device/vector_add.cl -seed=63 -o bin/vector_add.aocx -board pac_s10_dc
Level Two Title