- ``TARGET=gpu``: Sets compilation for GPU target.
- ``TARGET=fpga``: Sets compilation for FPGA target.
* ``DEBUG=1``: When provided will enable a debug compilation so that the HPVM passes will output debug prints. If instead it is desired to enable debug prints for specific passes, ``--debug-only=<DEBUG_TYPE>`` can be added to the ``FPGA_OPTFLAGS`` (used in FPGA compilation), ``HPVM_OPTFLAGS`` (used in CPU/GPU compilation), ``HCC-OPTS`` (used for the HeteroC++ frontend), and ``OCLBE_FLAGS`` (used for the llvm-to-opencl back end tool) variables. For example, debug prints for the FPGA back end pass can be enabled using: ``FPGA_OPTFLATS += --debug-only=DFG2LLVM_FPGA``. Note that this will only enable *compilation* debug prints. HPVM does not currently support compiling programs in debug mode (i.e. with ``-g`` flag).
* ``DEBUG=1``: When provided will enable a debug compilation so that the HPVM passes will output debug prints. If instead it is desired to enable debug prints for specific passes, ``--debug-only=<DEBUG_TYPE>`` can be added to the ``FPGA_OPTFLAGS`` (used in FPGA compilation), ``HPVM_OPTFLAGS`` (used in CPU/GPU compilation), ``HCC-OPTS`` (used for the Hetero-C++ frontend), and ``OCLBE_FLAGS`` (used for the llvm-to-opencl back end tool) variables. For example, debug prints for the FPGA back end pass can be enabled using: ``FPGA_OPTFLATS += --debug-only=DFG2LLVM_FPGA``. Note that this will only enable *compilation* debug prints. HPVM does not currently support compiling programs in debug mode (i.e. with ``-g`` flag).
* Additionally, the FPGA target supports the following extra variables:
- ``EMULATION=1``: Can be used to enable compilation of the FPGA kernels in EMULATION mode. This also generates the necessary host code in the binary that would launch the Intel FPGA Emulator instead of the actual FPGA.
...
...
@@ -90,5 +90,5 @@ Your own project
----------------
See `template <https://gitlab.engr.illinois.edu/llvm/hpvm-release/-/tree/main/hpvm/test/benchmarks/general_benchmarks/template>`__ for an example Makefile that you can use in your own project. As with the benchmarks, make sure ``Makefile.config`` is created as described above. In your makefile, you will need to specify the HPVM source file (i.e. the one that contains the HPVM DFG), any other source files that need to be linked in, the name of your application executable, and any linker and include flags. Make sure you include
``heterocc.h`` in your C/C++ project files to use the HeteroC++ api functions (found in
``heterocc.h`` in your C/C++ project files to use the Hetero-C++ api functions (found in
