SDSCC/SDS++ Compiler Commands

sdscc | sds++ [hardware_function_options] [system_options] [performance_estimation_options] [options_passed_through_to_cross_compiler] [-sds-pf platform_name] [-sds-pf-info platform_name] [-sds-pf-list] [-sds-sys-config configuration_name] [-sds-proc processor_name] [-target-os os_name] [-debug-xrf] [-debug-xrf-cc compiler] [-sds-pf-path path] [-sds-image image_name] [-verbose] [-version] [--help] [files]

[-sds-hw function_name source_file [-clkid clock_id_number] [-files hls_file_list] [-hls-target boolean_value] [-hls-target-flags "target_options"] [-hls-tcl hls_tcl_directives_file] [-shared-aximm] -sds-end]*

[[-perf-funcs function_name_list -perf-root function_name] | [-perf-est data_file][-perf-est-hw-only]]

[[-ac function_name:clock_id_number]*[-apm] [-bsp-config-file mss_file] [-bsp-config-merge-file mss_file][-disable-ip-cache] [-dm-sharing <0-3>] [-dmclkid clock_id_number] [-emulation mode] [-impl-strategy ] [-instrument-stub] [-maxthreads number] [-mno-bitstream][-mno-boot-files] [-rebuild-hardware] [-remote-ip-cache cache_directory] [-synth-strategy ] [-trace] [-trace-buffer depth] [-trace-no-sw] [-maxjobs ] [-sdcard ][-vpl-ini ini_file] [-xp parameter_value]]

The following command line options are applicable for anysds++invocation or your display information.

Hardware function options provide a means to consolidatesdscc/sds++options within aMakefileto simplify command line calls and make minimal modifications to a pre-existingMakefile.

APPSOURCES = add.cpp main.cpp EXECUTABLE = add.elf CROSS_COMPILE = arm-xilinx-linux-gnueabi- AR = ${CROSS_COMPILE}ar LD = ${CROSS_COMPILE}ld #CC = ${CROSS_COMPILE}g++ PLATFORM = zc702 SDSFLAGS = -sds-pf ${PLATFORM} \ -sds-hw add add.cpp -clkid 1 -sds-end \ -dmclkid 2 CC = sds++ ${SDSFLAGS} INCDIRS = -I.. LDDIRS = LDLIBS = CFLAGS = -Wall -g -c ${INCDIRS} LDFLAGS = -g ${LDDIRS} ${LDLIBS} SOURCES := $(patsubst %,../%,$(APPSOURCES)) OBJECTS := $(APPSOURCES:.cpp=.o) .PHONY: all all: ${EXECUTABLE} ${EXECUTABLE}: ${OBJECTS} ${CC} ${OBJECTS} -o $@ ${LDFLAGS} %.o: ../%.cpp ${CC} ${CFLAGS} $<

# synthesis directives create_clock -period  set_clock_uncertainty 27.0% config_rtl -reset_level low source  # end synthesis directives

A full bitstream compile can take much more time than a software compile, so thesdscc/sds++(referred to assds++) applications provide performance estimation options to compute the estimated runtime improvement for a set of hardware function calls.

In the Application Project Settings pane, to invoke the estimator, select theEstimate Performancecheck box. This enables performance estimation for the current build configuration and builds the project.

Figure:Setting Estimate Performance in Application Project Settings

Estimating the speed-up is a two phase process:

1. TheSDSoCenvironment compiles the hardware functions and generates the system. Instead of synthesizing the system to bitstream, thesds++computes an estimate of the performance based on estimated latencies for the hardware functions and data transfer time estimates for the callers of hardware functions.
2. In the generated Performance Report, to determine a performance baseline and the performance estimate, selectClick Hereto run an instrumented version of the software on the target .

See theSDSoC Environment Getting Started Tutorial(UG1028)for a tutorial on how to use the Performance Report.

You can also generate a performance estimate from the command line. As a first pass to gather data about software runtime, use the-perf-funcsoption to specify functions to profile and-perf-rootto specify the root function encompassing calls to the profiled functions.

Thesds++system compiler then automatically instruments these functions to collect runtime data when the application is run on a board. When you run an instrumented application on the target, the program creates a file on the SD card calledswdata.xml, which contains the runtime performance data for the run.

Copy theswdata.xmlto the host, and run a build that estimates the performance gain on a per hardware function caller basis and for the top-level function specified by the–perf-rootfunction in the first pass run. Use the–perf-estoption to specifyswdata.xmlas input data for this build.

TheSDSoCenvironment uses the same GNUArmcross-compiler toolchains included with theXilinxSoftware Development Kit (SDK).

The Linaro-based GCC compiler toolchains support theZynq-7000 SoCandZynq UltraScale+ MPSoCfamily devices. This section includes additional information on toolchain usage.

When compiling and linking applications, use only object files and libraries built using the same compiler toolchain and options as those used by theSDSoCenvironment. AllSDSoCprovided software libraries and software components (Linux kernel, root filesystem, BSP libraries, and other pre-built libraries) are built with the included toolchains. If you usesdscc/sds++(referred to assds++) to compile object files, the tools automatically insert a small number of options. If you invoke the underlying toolchains, you must use the same options.

For example, if you use a differentZynq-7000 SoCfloating-point application binary interface (ABI), your binary objects are incompatible and cannot be linked withSDSoCZynq-7000binary objects and libraries.

The following table summarizes thesds++usage ofZynq-7000 SoCtoolchains and options. Where options are listed, you need to specify them only if you use the toolchaingccandg++commands directly instead of invokingsds++.

The following table summarizessds++usage ofZynq UltraScale+ MPSoCCortex™-A53 toolchains and options. Where options are listed, you only need to specify them if you use the toolchaingccandg++commands directly instead of invokingsds++.

The following table summarizes thesds++usage ofZynq UltraScale+ MPSoCCortex-R5 toolchains and options. Where options are listed, you need to specify them only if you use the toolchaingccandg++commands directly instead of invokingsds++.

For source files that do not contain hardware accelerators or callers but do use NEON intrinsics, you can either compile them directly using the GNU toolchain and link the objects withsds++, or you can add thesds++command line option-mno-irfor these source files. This option prevents clang-based tools from being invoked to create an intermediate representation (IR) used in analysis. You are programmatically aware that they are not required (such as no accelerators or callers).

For the latter solution, if you are using theSDSoCenvironment, you can apply the option on a per-file basis by right-clicking the source file, selectPropertiesand go to theSettingsdialog box underC/C++ Build Settings>Settings.

Figure:Build Settings