After simulation completes, click Run under C Synthesis.
The default output format for C synthesis is RTL. This is to let you evaluate the results of high-level synthesis before exporting the Vivado IP or Vitis kernel for further use in an embedded system design or Data Center acceleration.
Again, you can view the
dct::synthesis transcript displayed in the Output window as the design is synthesized. Examine the transcript to see what steps the tool takes during synthesis. The following list describes some of the steps listed:
Project and solution initialization loads source and constraints files, and configures the active solution for synthesis.
Start compilation reads source files into memory.
Interface detection and setup reviews and generates port and block interfaces for the function.
Burst read and write analysis for ports/interfaces.
Compiler transforms code to operations.
Performs Synthesizeability checks.
Automatic pipelining of loops at tripcount threshold.
Unrolling loops, both automatic and user-directed.
Balance expressions using associative and commutative properties.
Loop flattening to reduce loop hierarchy.
Partial write detection (writing part of a memory word)
Finish architecture synthesis, start scheduling.
End scheduling, generate RTL code.
Report FMax and loop constraint status.
The Vitis HLS tool also automatically inlines small functions, dissolving the logic into the higher-level calling functions, and pipelines small loops with limited iterations. These features are configurable by user directives in the
hls_config.cfg file, or pragmas in the
After synthesis completes you will see the Run command marked with a green circle and a checkmark to indicate it has been succesfully run. However it will also have a yellow Caution triangle to indicate that the
output.format was RTL and no IP or XO was generated from the design. This output will need to be generated before the HLS component can be used in downstream tools such as the Vivado Design Suite, or in a System project.
After synthesis completes you will also see Reports under C Synthesis is populated with a Summary report, Synthesis, Function Call Graph, Schedule Viewer, Dataflow Viewer (for Dataflow designs), and Kernel Guidance. You can click to view any of these reports.
Open the Synthesis report. This is the Synthesis Summary report that would previously open after synthesis. Now you can access the report when needed.
Look at the top of the Performance and Resource Estimates table in the figure above. It displays a number of icons that enable different features of the report. Also notice the icon on the Timing Report that changes timing from ns to MHz.
Notice that the various sub-functions from the
dct.cpp source are not reported in the synthesis results. This is because the tool has inlined these functions automatically. You can disable the inlining of specific functions by adding the INLINE OFF pragma or directive for the function, or by adding the DATAFLOW optimization to the design, which you will be doing later in this tutorial.
The HLS tool also automatically pipelined loops that have fewer than a specified number of iterations. Pipelining loops with fewer than 64 iterations is the default setting. When pipelining, the tool tries to achieve an II of 1. The II is the number of clock cycles before the next iteration of the loop is processed. When pipelining the loop with
II=1, you want the next iteration to start at the next clock cycle.