Article ID: 000096220 Content Type: Error Messages Last Reviewed: 08/21/2023

main_functor.cpp:34 Compiler Error: Pointer argument 0 to 'intersector_func' HDL Function Call is not a function argument!

Environment

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Description

Due to a problem in the Intel® OneAPI Base Toolkit (Base Kit) version 2023.2 in the DevCloud Environment, you might see an error like this when compiling an RTL library.

Compiler Error: A pointer passed to HDL Library component must satify all the criteria:
Compiler Error:  1. Must be a global or constant adress space pointer. < style="margin-left: 40px;">
Compiler Error:  2. Must be a kernal argument. < style="margin-left: 40px;">
Compiler Error:  3. Must be marked with 'restrict' keyword to prevemt aliasing. < style="margin-left: 40px;">
Compiler Error:  4. Must have no other uses besides a single HDL library component OR < style="margin-left: 40px;">
Compiler Error:    must have all its uses, including by all HDL library components, as read-only. < style="margin-left: 40px;">
Error: Optimizer FAILED

Resolution

To work around this problem, download and install the 2023.2.1 patch from the links below

  1. Determine where the 2023.2 oneAPI base toolkit is installed. The FPGA Add-on will be located inside of the toolkit installation directory in the ‘oclfpga’ folder.
    1. For Linux, this will be ‘<install-dir>/intel/oneapi/compiler/2023.2.0/linux/lib/oclfpga’, where <install-dir> is typically either ‘/opt’ or ‘~’.
    2. For Windows, this will usually be ‘C:\Program Files (x86)\Intel\oneAPI\compiler\2023.2.0\windows\lib\oclfpga’.
  2. Rename the existing ‘oclfpga’ directory to something else, e.g., ‘oclfpga.bak’ or ‘oclfpga.prev’.
  3. Unpack the given archive, .tar.gz for Linux and .zip for Windows, to extract the ‘oclfpga’ folder and place it in ‘intel/oneapi/compiler/2023.2.0/<platform>/lib’, where <platform> is either ‘windows’ or ‘Linux’ (see above).
  4. (Optional) Remove the backup folder created in Step ‘2’ after testing.

This problem is scheduled to be fixed in a future release of the Intel® OneAPI Base Toolkit (Base Kit).

Related Products

This article applies to 1 products

Intel® Programmable Devices

1