TMS320C6000编译器v7.4用户指南

TMS320C6000

Optimizing

需积分: 10 144 浏览量更新于2024-07-09 收藏 1.09MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"TMS320C6000 Optimizing Compiler v7.4 User's Guide SPRU187U" 这份用户指南是关于TMS320C6000系列数字信号处理器（DSP）的优化编译器v7.4的详细文档。TMS320C6000是一款高性能的 DSP 平台，广泛应用于音频、视频、通信和图像处理等领域的嵌入式系统。该编译器是开发这些应用的关键工具，能够将C和C++源代码转化为高效的机器代码。 1. 软件开发工具概述软件开发工具包括编译器、调试器、性能分析器等，它们帮助开发者编写、优化和测试代码。这些工具旨在提高代码质量和执行效率，确保在TMS320C6000硬件平台上运行时达到最佳性能。 1.1 ANSI/ISO标准 C/C++编译器遵循ANSI（美国国家标准协会）和ISO（国际标准化组织）制定的C和C++编程语言标准，以保证代码的可移植性和一致性。 1.2 C/C++编译器介绍 1.2.1 ANSI/ISO标准：编译器支持C和C++的ANSI/ISO标准，确保编写的代码符合业界通用的编程规范。 1.2.2 输出文件：编译过程会生成不同的输出文件，如对象文件、库文件和可执行文件。 1.2.3 编译器接口：提供了与用户交互的命令行界面或集成开发环境（IDE）的接口。 1.2.4 辅助工具：除了编译器外，还包含其他辅助工具，如预处理器、链接器和汇编器。 2. 使用C/C++编译器 2.1 关于编译器：编译器是将高级语言转换为针对TMS320C6000 DSP的机器码的关键工具。 2.2 调用编译器：开发者可以通过命令行参数来启动和配置编译器。 2.3 改变编译器行为的选项： - 常用选项：如优化级别、警告控制、代码生成模式等。 - 杂项有用选项：如内存模型设置、内存分配策略等。 - 运行时模型选项：用于选择不同内存模型，以适应不同应用需求。 - 选择目标CPU版本：指定要编译的目标CPU型号。 - 符号调试和性能分析选项：支持GDB调试和性能分析工具。 - 指定文件名：控制输入输出文件的命名和位置。 - 文件名解析：调整编译器如何解释文件路径和名称。 - 文件处理：控制编译器对C源文件的处理方式。 - 扩展名解释和命名：定义编译器如何处理不同扩展名的文件。 - 指定目录：设置包含头文件和库的搜索路径。 - 链接器选项：影响链接过程，如静态或动态链接。 - 不推荐的选项：一些旧版或过时的选项，可能在新版本中被替换或移除。 2.4 环境变量控制编译器：通过设置特定的环境变量，可以全局地影响编译器的行为和配置。这份用户指南为开发者提供了全面的指导，帮助他们充分利用TMS320C6000 Optimizing Compiler v7.4，实现高效、优化的代码生成，以满足高性能嵌入式系统的开发需求。通过理解和掌握编译器的选项和特性，开发者能够更好地控制代码质量，提高程序运行速度，并有效地调试和分析代码性能。

资源详情

资源推荐

C/C++ Compiler Overview

www.ti.com

• The assembler translates assembly language source files into machine language relocatable object

files. The TMS320C6000 Assembly Language Tools User's Guide explains how to use the assembler.

• The linker combines relocatable object files into a single absolute executable object file. As it creates

the executable file, it performs relocation and resolves external references. The linker accepts

relocatable object files and object libraries as input. See Chapter 5. The TMS320C6000 Assembly

Language Tools User's Guide provides a complete description of the linker.

• The archiver allows you to collect a group of files into a single archive file, called a library.

Additionally, the archiver allows you to modify a library by deleting, replacing, extracting, or adding

members. One of the most useful applications of the archiver is building a library of object files. The

TMS320C6000 Assembly Language Tools User's Guide explains how to use the archiver.

• The run-time-support libraries contain the standard ISO C and C++ library functions, compiler-utility

functions, floating-point arithmetic functions, and C I/O functions that are supported by the compiler.

See Chapter 8.

You can use the library-build utility to build your own customized run-time-support library. See

Section 8.5. Source code for the standard run-time-support library functions for C and C++ are

provided in the self-contained rtssrc.zip file.

• The hex conversion utility converts an object file into other object formats. You can download the

converted file to an EPROM programmer. The TMS320C6000 Assembly Language Tools User's Guide

explains how to use the hex conversion utility and describes all supported formats.

• The absolute lister accepts linked object files as input and creates .abs files as output. You can

assemble these .abs files to produce a listing that contains absolute, rather than relative, addresses.

Without the absolute lister, producing such a listing would be tedious and would require many manual

operations. The TMS320C6000 Assembly Language Tools User's Guide explains how to use the

absolute lister.

• The cross-reference lister uses object files to produce a cross-reference listing showing symbols,

their definitions, and their references in the linked source files. The TMS320C6000 Assembly

Language Tools User's Guide explains how to use the cross-reference utility.

• The C++ name demangler is a debugging aid that converts names mangled by the compiler back to

their original names as declared in the C++ source code. As shown in Figure 1-1, you can use the C++

name demangler on the assembly file that is output by the compiler; you can also use this utility on the

assembler listing file and the linker map file. See Chapter 9.

• The disassembler decodes object files to show the assembly instructions that they represent. The

TMS320C6000 Assembly Language Tools User's Guide explains how to use the disassembler.

• The main product of this development process is an executable object file that can be executed in a

TMS320C6000 device. You can use one of several debugging tools to refine and correct your code.

Available products include:

– An instruction-level and clock-accurate software simulator

– An XDS emulator

1.2 C/C++ Compiler Overview

The following subsections describe the key features of the compiler.

1.2.1 ANSI/ISO Standard

The C and C++ language features in the compiler are implemented in conformance with these ISO

standards:

• ISO-standard C

The C/C++ compiler conforms to the C Standard ISO/IEC 9889:1990. The ISO standard supercedes

and is the same as the ANSI C standard. There is also a 1999 version of the ISO standard, but the TI

compiler conforms to the 1990 standard, not the 1999 standard. The language is also described in the

second edition of Kernighan and Ritchie's The C Programming Language (K&R).

• ISO-standard C++

The C/C++ compiler conforms to the C++ Standard ISO/IEC 14882:1998. The language is also

described in Ellis and Stroustrup's The Annotated C++ Reference Manual (ARM), but this is not the

Introduction to the Software Development Tools SPRU187U–July 2012

Submit Documentation Feedback

www.ti.com

C/C++ Compiler Overview

standard. The compiler also supports embedded C++. For a description of unsupported C++ features,

see Section 6.2.

• ISO-standard run-time support

The compiler tools come with an extensive run-time library. All library functions conform to the ISO

C/C++ library standard. The library includes functions for standard input and output, string

manipulation, dynamic memory allocation, data conversion, timekeeping, trigonometry, and exponential

and hyperbolic functions. Functions for signal handling are not included, because these are target-

system specific. For more information, see Chapter 8.

1.2.2 Output Files

These types of output files are created by the compiler:

• COFF object files

Common object file format (COFF) allows you to define your system's memory map at link time. This

maximizes performance by enabling you to link C/C++ code and data objects into specific memory

areas. COFF also supports source-level debugging.

• ELF object files

Executable and linking format (ELF) enables supporting modern language features like early template

instantiation and exporting inline functions.

1.2.3 Compiler Interface

These features enable interfacing with the compiler:

• Compiler program

The compiler tools include a compiler program (cl6x) that you use to compile, optimize, assemble, and

link programs in a single step. For more information, see Section 2.1

• Flexible assembly language interface

The compiler has straightforward calling conventions, so you can write assembly and C functions that

call each other. For more information, see Chapter 7.

1.2.4 Utilities

These features are compiler utilities:

• Library-build utility

The library-build utility lets you custom-build object libraries from source for any combination of run-

time models. For more information, see Section 8.5.

• C++ name demangler

The C++ name demangler (dem6x) is a debugging aid that translates each mangled name it detects in

compiler-generated assembly code, disassembly output, or compiler diagnostic messages to its

original name found in the C++ source code. For more information, see Chapter 9.

• Hex conversion utility

For stand-alone embedded applications, the compiler has the ability to place all code and initialization

data into ROM, allowing C/C++ code to run from reset. The COFFor ELF files output by the compiler

can be converted to EPROM programmer data files by using the hex conversion utility, as described in

the TMS320C6000 Assembly Language Tools User's Guide.

SPRU187U–July 2012 Introduction to the Software Development Tools

Submit Documentation Feedback

Chapter 2

SPRU187U–July 2012

Using the C/C++ Compiler

The compiler translates your source program into machine language object code that the TMS320C6000

can execute. Source code must be compiled, assembled, and linked to create an executable object file. All

of these steps are executed at once by using the compiler.

Topic ........................................................................................................................... Page

2.1 About the Compiler ........................................................................................... 19

2.2 Invoking the C/C++ Compiler .............................................................................. 19

2.3 Changing the Compiler's Behavior With Options ................................................... 20

2.4 Controlling the Compiler Through Environment Variables ...................................... 39

2.5 Precompiled Header Support .............................................................................. 41

2.6 Controlling the Preprocessor .............................................................................. 42

2.7 Understanding Diagnostic Messages ................................................................... 45

2.8 Other Messages ................................................................................................ 48

2.9 Generating Cross-Reference Listing Information (--gen_acp_xref Option) ................ 48

2.10 Generating a Raw Listing File (--gen_acp_raw Option) ........................................... 48

2.11 Using Inline Function Expansion ......................................................................... 50

2.12 Interrupt Flexibility Options (--interrupt_threshold Option) ..................................... 53

2.13 Linking C6400 Code With C6200/C6700/Older C6400 Object Code ........................... 54

2.14 Using Interlist ................................................................................................... 54

2.15 Generating and Using Performance Advice .......................................................... 55

2.16 Controlling Application Binary Interface ............................................................... 55

2.17 Enabling Entry Hook and Exit Hook Functions ..................................................... 57

Using the C/C++ Compiler SPRU187U–July 2012

Submit Documentation Feedback

www.ti.com

About the Compiler

2.1 About the Compiler

The compiler lets you compile, assemble, and optionally link in one step. The compiler performs the

following steps on one or more source modules:

• The compiler accepts C/C++ source code and assembly code, and produces object code.

You can compile C, C++, and assembly files in a single command. The compiler uses the filename

extensions to distinguish between different file types. See Section 2.3.9 for more information.

• The linker combines object files to create a static executable or dynamic object file. The linker is

optional, so you can compile and assemble many modules independently and link them later. See

Chapter 5 for information about linking the files.

Invoking the Linker

NOTE: By default, the compiler does not invoke the linker. You can invoke the linker by using the --

run_linker compiler option.

For a complete description of the assembler and the linker, see the TMS320C6000 Assembly Language

Tools User's Guide.

2.2 Invoking the C/C++ Compiler

To invoke the compiler, enter:

cl6x [options] [filenames] [--run_linker [link_options] object files]]

cl6x Command that runs the compiler and the assembler.

options Options that affect the way the compiler processes input files. The options are

listed in Table 2-5 through Table 2-32.

filenames One or more C/C++ source files, assembly language source files, linear

assembly files, or object files.

--run_linker Option that invokes the linker. The --run_linker option's short form is -z. See

Chapter 5 for more information.

link_options Options that control the linking process.

object files Name of the additional object files for the linking process.

The arguments to the compiler are of three types:

• Compiler options

• Link options

• Filenames

The --run_linker option indicates linking is to be performed. If the --run_linker option is used, any compiler

options must precede the --run_linker option, and all link options must follow the --run_linker option.

Source code filenames must be placed before the --run_linker option. Additional object file filenames can

be placed after the --run_linker option.

For example, if you want to compile two files named symtab.c and file.c, assemble a third file named

seek.asm, and link to create an executable program called myprogram.out, you will enter:

cl6x symtab.c file.c seek.asm --run_linker --library=lnk.cmd

--library=rts6200.lib --output_file=myprogram.out

SPRU187U–July 2012 Using the C/C++ Compiler

Submit Documentation Feedback

Changing the Compiler's Behavior With Options

www.ti.com

2.3 Changing the Compiler's Behavior With Options

Options control the operation of the compiler. This section provides a description of option conventions

and an option summary table. It also provides detailed descriptions of the most frequently used options,

including options used for type-checking and assembling.

For a help screen summary of the options, enter cl6x with no parameters on the command line.

The following apply to the compiler options:

• Options are preceded by one or two hyphens.

• Options are case sensitive.

• Options are either single letters or sequences of characters.

• Individual options cannot be combined.

• An option with a required parameter should be specified with an equal sign before the parameter to

clearly associate the parameter with the option. For example, the option to undefine a constant can be

expressed as --undefine=name. Although not recommended, you can separate the option and the

parameter with or without a space, as in --undefine name or -undefinename.

• An option with an optional parameter should be specified with an equal sign before the parameter to

clearly associate the parameter with the option. For example, the option to specify the maximum

amount of optimization can be expressed as -O=3. Although not recommended, you can specify the

parameter directly after the option, as in -O3. No space is allowed between the option and the optional

parameter, so -O 3 is not accepted.

• Files and options except the --run_linker option can occur in any order. The --run_linker option must

follow all other compile options and precede any link options.

You can define default options for the compiler by using the C6X_C_OPTION environment variable. For a

detailed description of the environment variable, see Section 2.4.1.

Table 2-5 through Table 2-32 summarize all options (including link options). Use the references in the

tables for more complete descriptions of the options.

Table 2-1. Processor Options

Option Alias Effect Section

--silicon_version=id -mv Selects target version. Defaults to 6200. Section 2.3.4

--big_endian -me Produces object code in big-endian format Section 2.13

--abi={coffabi|eabi} Selects application binary interface. Default is coffabi. Section 2.16

Table 2-2. Optimization Options

(1)

Option Alias Effect Section

--opt_level=0 -O0 Optimizes register usage Section 3.1

--opt_level=1 -O1 Uses -O0 optimizations and optimizes locally Section 3.1

--opt_level=2 -O2 or -O Uses -O1 optimizations and optimizes globally (default) Section 3.1

--opt_level=3 -O3 Uses -O2 optimizations and optimizes the file Section 3.1

Section 3.6

--opt_for_space=n -ms Controls code size on four levels (0, 1, 2, and 3) Section 3.5

(1)

Note: Machine-specific options (see Table 2-11) can also affect optimization.

Table 2-3. Debug Options

Option Alias Effect Section

--symdebug:dwarf -g Enables symbolic debugging Section 2.3.5

Section 3.14.3.1

--symdebug:coff Enables symbolic debugging using the alternate STABS debugging Section 2.3.5

format. STABS format is not supported for C6400+ or C674x, or Section 3.14.3.1

when using ELF.

--symdebug:none Disables all symbolic debugging Section 2.3.5

Using the C/C++ Compiler SPRU187U–July 2012

Submit Documentation Feedback

剩余276页未读，继续阅读

qqqljx

粉丝: 17
资源: 10

TMS320C6000编译器v7.4用户指南

tms320c6000-optimizing_compiler_users_guide_v7.4.pdf

tms320c6000-optimizing_compiler_users_guide.pdf

NotADirectoryError: [WinError 267] 目录名称无效。: 'D:\\tms\\GNSS-R\\tables\\cyg01.ddmi.s20230717-000000-e20230717-235959.l1.power-brcs.a31.d32.nc'

tms320c6000系列dsp编程工具与指南.pdf

tms-web-core-v2.0.5.0 载

[root@tms-app-t5 ~]# find / -type d -name webapps /usr/local/src/apache-tomcat-8.5.75/webapps /csair/apache-tomcat-8.5.75/webapps 我要获取

tms320c6000系列dsp编程工具与指南 csdn

tms320c6000实例讲解

tms320c6000系列dsps的原理与应用

TMS320 C6000系列 DSP之 CCS5.5 仿真调试

tms320f2837xd技术参考手册-中文chinese

tms320f2837xd中文手册tms320f2837xd技术参考手册-

对于TMS320C6000系列，McBSP的功能有什么 参数RAM的容量为2KB，总共可以存放多少组EDMA传输控制参数。

tms async32 1.5.2.0 - d3-x10

tms320f28055 spi

创龙 tms320f28335开发例程使用手册.pdf

tms320f2837xd技术参考手册-第10章:模数转换器(adc)

matlab基于模型设计(入门到精通)tms320f28335.pdf

tms320f2837xd中文手册

手把手教你学dsp-基于tms320x281x_458页_23.4m_高清书签版.pdf

最新资源

对于TMS320C6000系列，McBSP的功能有什么参数RAM的容量为2KB，总共可以存放多少组EDMA传输控制参数。