User`s guide

ManualsBrandsMotorola ManualsComputer equipmentDSP56800

Target Settings

DSP56800E-Specific Target Settings Panels

Targeting MC56F83xx/DSP5685x Controllers

The compiler generates hardware DO loops for two situations:

1. Aggregate (array and structure) initializations, and for struct copy, under any of

these conditions:

• The aggregate is byte aligned, and the aggregate size is greater than four bytes.

• The aggregate is word aligned, and the aggregate size is greater than four

words.

• The aggregate is long aligned, the aggregate size is greater than eight words,

and the Global Optimizations panel specifies Optimize for Smaller Code Size.

• The aggregate is long aligned, the aggregate size is greater than 32 words, and

the Global Optimizations panel specifies Optimize for Faster Execution.

Zero-initialized

globals live in

data instead of

BSS checkbox

Checked — Globals initialized to zero

reside in the .data section.

Clear — Globals initialized to zero reside in

the .bss section.

Create Assembly

Output checkbox

Checked — Assembler generates

assembly code for each C file.

Clear — Assembler does not generate

assembly code for each C file.

The pragma #asmoutput overrides

this option for individual files.

Pipeline Conflict

Detection Inline

ASM list box

Specifies pipeline conflict detection during

compiling of inline assembly source code:

• Not Detected — compiler does not

check for conflicts

• Conflict error — compiler issues

error messages if it detects

conflicts

• Conflict Error/Hardware Stall

Warning — compiler issues error

messages if it detects conflicts,

warnings if it detects hardware

stalls

For more information about pipeline

conflicts, see the explanations of

pragmas check_c_src_pipeline and

check_inline_asm_pipeline.

Pipeline Conflict

Detection C

Language list

box