The following crash can occur when using the Intel^® FPGA Emulation Platform on Windows system:

Stack dump:
0. Running pass 'CallGraph Pass Manager' on module 'main'

This crash is caused by the use of high number of function calls in the design (more than 10,000).

internal compiler error: node internal validation failed

OpenCL™ kernels with names longer than 61 characters might fail in the Intel^® Quartus^® Prime Pro Edition compiler with an error similar to the following error:

Error (16045): Instance "...|<long_kernel_name>_cra_slave_inst" instantiates 
undefined entity "<long_kernel_name>_function_cra_slave" File: <filename> Line: 
<linenumber>

Terminating the host process in BSPs (all versions of a10_ref, s10_ref, and s10mx_ref) can cause the machine to crash or freeze when OpenCL is running. BSPs require the host user process to stay active during certain operations, such as DMA transfers. If you terminate the host process while such operations are active, the operating system crashes.

If your BSP is affected by this issue, you should avoid performing the following:

• Pressing Ctrl + C keys combination
• Using assertions
• Calling the exit() function
• Performing any abnormal termination in the host programs, such as null dereference, bus error, uncaught exception, and so on.

Race conditions can occur between enqueue and dequeue buffer operations and host pipe operations. These conditions can results in incorrect data being read or written.

A way to ensure that buffer operations do not occur in parallel with host pipe API calls is to do buffer operations as blocking calls before the first host pipe operation and after you are certain that the last host pipe operation has been completed (for example, all the data is read back).

This issue affects the Intel^® Arria^® 10 GX FPGA Development Kit Reference Platform and the Intel^® Stratix^® 10 GX FPGA Development Kit Reference Platform.

• Rewrite the host application to limit the query for clGetDeviceIDs to the actual number of devices.
• Rewrite the host application to use clGetDeviceInfo to query which devices are available. Calling clGetDeviceInfo with the CL_DEVICE_AVAILABLE flag correctly reports that extraneous devices are unavailable.
• Rewrite the host application to only call clCreateContext with the actual number of devices. Calling clCreateContext with extraneous devices will fail with the error CL_DEVICE_NOT_AVAILABLE.
• Set the environment variable CL_OVERRIDE_NUM_DEVICES_INTELFPGA to the correct number of devices. Doing so fixes the erroneous behavior of clGetDeviceIDs.