Documentation Center

  • Trial Software
  • Product Updates

Optimization Pane: General

The Optimization > General pane includes the following parameters:

Optimization Pane: General Tab Overview

Set up optimizations for a model's active configuration set. Optimizations are set for both simulation and code generation.

Tips

  • To open the Optimization pane, in the Simulink® Editor, select Simulation > Model Configuration Parameters > Optimization.

  • Simulink Coder™ optimizations appear only when the Simulink Coder product is installed on your system. Selecting a GRT-based or ERT-based system target file changes the available options. ERT-based target optimizations require a Embedded Coder® license when generating code. See the Dependencies sections below for licensing information for each parameter.

See Also

Block reduction

Reduce execution time by collapsing or removing groups of blocks.

Settings

Default: On

On

Simulink software searches for and reduces the following block patterns:

  • Redundant type conversions — Unnecessary type conversion blocks, such as an int type conversion block with an input and output of type int.

  • Dead code — Blocks or signals in an unused code path.

  • Fast-to-slow Rate Transition block in a single-tasking system — Rate Transition blocks with an input frequency faster than its output frequency.

Off

Simulink software does not search for block patterns that can be optimized. Simulation and generated code are not optimized.

Tips

  • When you select Block reduction, Simulink software collapses certain groups of blocks into a single, more efficient block, or removes them entirely. This results in faster execution during model simulation and in generated code.

  • Block reduction does not change the appearance of the source model.

  • Tunable parameters do not prevent a block from being reduced by dead code elimination.

  • Once block reduction takes place, Simulink software does not display the sorted order for blocks that have been removed.

  • If you have a Simulink Coder license, block reduction is intended to remove only the generated code that represents execution of a block. Other supporting data, such as definitions for sample time and data types might remain in the generated code.

Dead Code Elimination.  Any blocks or signals in an unused code path are eliminated from generated code.

  • The following conditions need to be met for a block to be considered part of an unused code path:

    • All signal paths for the block end with a block that does not execute. Examples of blocks that do not execute include Terminator blocks, disabled Assertion blocks, S-Function blocks configured for block reduction, and To Workspace blocks when MAT-file logging is disabled for code generation.

    • No signal paths for the block include global signal storage downstream from the block.

  • Tunable parameters do not prevent a block from being reduced by dead code elimination.

  • Consider the signal paths in the following block diagram.

    If you check Block reduction, Simulink Coder software responds to each signal path as follows:

    For Signal Path...Simulink Coder Software...
    In1 to Out1Always generates code because dead code elimination conditions are not met.
    In2 to TerminatorNever generates code because dead code elimination conditions are met.
    In3 to ScopeGenerates code if MAT-file logging is enabled and eliminates code if MAT-file logging is disabled.

Command-Line Information

Parameter: BlockReduction
Type: string
Value: 'on' | 'off'
Default: 'on'

Recommended Settings

ApplicationSetting
DebuggingOff (for simulation and during development)
No impact (for production code generation)
TraceabilityOff
EfficiencyOn
Safety precautionOff

See Also

Conditional input branch execution

Improve model execution when the model contains Switch and Multiport Switch blocks.

Settings

Default: On

On

Executes only the blocks required to compute the control input and the data input selected by the control input. This optimization speeds execution of code generated from the model. Limits to Switch block optimization:

  • Only blocks with -1 (inherited) or inf (Constant) sample time can participate.

  • Blocks with outputs flagged as test points cannot participate.

  • No multirate block can participate.

  • Blocks with states cannot participate.

  • Only S-functions with option SS_OPTION_CAN_BE_CALLED_CONDITIONALLY set can participate.

Off

Executes all blocks driving the Switch block input ports at each time step.

Command-Line Information

Parameter: ConditionallyExecuteInputs
Type: string
Value: 'on' | 'off'
Default: 'on'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityOn
EfficiencyOn (execution), No impact (ROM, RAM)
Safety precautionNo impact

See Also

Implement logic signals as Boolean data (vs. double)

Controls the output data type of blocks that generate logic signals.

Settings

Default: On

On

Blocks that generate logic signals output a signal of boolean data type. This reduces the memory requirements of generated code.

Off

Blocks that generate logic signals output a signal of double data type. This ensures compatibility with models created by earlier versions of Simulink software.

Tips

  • Setting this option on reduces the memory requirements of generated code, because a Boolean signal typically requires one byte of storage compared to eight bytes for a double signal.

  • Setting this option off allows the current version of Simulink software to run models that were created by earlier versions of Simulink software that supported only signals of type double.

  • This optimization affects the following blocks:

    • Logical Operator block – This parameter affects only those Logical Operator blocks whose Output data type parameter specifies Inherit: Logical (see Configuration Parameters: Optimization). If this parameter is selected, such blocks output a signal of boolean data type; otherwise, such blocks output a signal of double data type.

    • Relational Operator block – This parameter affects only those Relational Operator blocks whose Output data type parameter specifies Inherit: Logical (see Configuration Parameters: Optimization). If this parameter is selected, such blocks output a signal of boolean data type; otherwise, such blocks output a signal of double data type.

    • Combinatorial Logic block – If this parameter is selected, Combinatorial Logic blocks output a signal of boolean data type; otherwise, they output a signal of double data type. See Combinatorial Logic in the Simulink Reference for an exception to this rule.

    • Hit Crossing block – If this parameter is selected, Hit Crossing blocks output a signal of boolean data type; otherwise, they output a signal of double data type.

Dependencies

  • This parameter is disabled for models created with a version of Simulink software that supports only signals of type double.

Command-Line Information

Parameter: BooleanDataType
Type: string
Value: 'on' | 'off'
Default: 'on'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn
Safety precautionOn

See Also

Application lifespan (days)

Specify how long (in days) an application that contains blocks depending on elapsed or absolute time should be able to execute before timer overflow.

Settings

Default: inf
Min: Must be greater than zero
Max: inf

Enter a positive (nonzero) scalar value (for example, 0.5) or inf.

If you are licensed for the Embedded Coder product and select an ERT target for your model, the default value for Application lifespan (days) is 1.

This parameter is ignored when you are operating your model in external mode, have Mat-file logging enabled, or have a continuous sample time because a 64 bit timer is required in these cases.

Tips

  • Specifying a lifespan, along with the simulation step size, determines the data type used by blocks to store absolute time values.

  • For simulation, setting this parameter to a value greater than the simulation time will ensure time does not overflow.

  • Simulink software evaluates this parameter first against the model workspace. If this does not resolve the parameter, Simulink software then evaluates it against the base workspace.

  • The Application lifespan also determines the word size used by timers in the generated code, which can lower RAM usage. For more information, see Timing ServicesTiming Services in the Simulink Coder documentation.

  • Application lifespan, when combined with the step size of each task, determines the data type used for integer absolute time for each task, as follows:

    • If your model does not require absolute time, this option affects neither simulation nor the generated code.

    • If your model requires absolute time, this option optimizes the word size used for storing integer absolute time in generated code. This ensures that timers do not overflow within the lifespan you specify. If you set Application lifespan to inf, two uint32 words are used.

    • If your model contains fixed-point blocks that require absolute time, this option affects both simulation and generated code.

    For example, using 64 bits to store timing data enables models with a step size of 0.001 microsecond (10E-09 seconds) to run for more than 500 years, which would rarely be required. To run a model with a step size of one millisecond (0.001 seconds) for one day would require a 32-bit timer (but it could continue running for 49 days).

  • A timer will allocate 64 bits of memory if you specify a value of inf.

  • To minimize the amount of RAM used by time counters, specify a lifespan no longer than necessary.

  • Must be the same for top and referenced models.

  • Optimize the size of counters used to compute absolute and elapsed time.

Command-Line Information

Parameter: LifeSpan
Type: string
Value: positive (nonzero) scalar value or inf
Default: 'inf'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyFinite value
Safety precautioninf

See Also

Use integer division to handle net slopes that are reciprocals of integers

The Fixed-Point Designer™ software performs net slope correction using integer division to handle net slopes that are reciprocals of integers when simplicity and accuracy conditions are met.

Settings

Default: Off

On

Perform net slope correction using integer division when simplicity and accuracy conditions are met.

Off

Perform net slope correction using integer multiplication followed by shifts.

Tips

  • This optimization affects both simulation and code generation.

  • When a change of fixed-point slope is not a power of two, net slope correction is necessary. Normally, net slope correction uses an integer multiplication followed by shifts. Enabling this new optimization replaces the multiplication and shifts with an integer division under certain simplicity and accuracy conditions.

  • Performing net slope correction using integer division is not always more efficient than using multiplication followed by shifts. Ensure that the target hardware supports efficient division.

  • To ensure that this optimization occurs, you must:

    • Set the word length of the block to ensure that the software can perform division using the production target long data type. This avoids using multiword operations.

    • Set the Signed integer division rounds to configuration parameter setting on the Hardware Implementation > Production hardware subpane to Zero or Floor. The optimization does not occur if this parameter is set to Undefined.

    • Set the Integer rounding mode parameter of the block to Simplest or to the value of the Signed integer division rounds to configuration parameter setting on the Hardware Implementation > Production hardware subpane.

Dependency

This parameter requires a Fixed-Point Designer license.

Command-Line Information

Parameter: UseIntDivNetSlope
Type: string
Value: 'on' | 'off'
Default: 'off'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn (when target hardware supports efficient division)
Off (otherwise)
Safety precautionNo impact

See Also

Use floating-point multiplication to handle net slope corrections

The Fixed-Point Designer software uses floating-point multiplication to perform net slope correction for floating-point to fixed-point casts.

Settings

Default: Off

On

Use floating-point multiplication to perform net slope correction for floating-point to fixed-point casts.

Off

Use division to perform net slope correction for floating-point to fixed-point casts.

Tips

  • This optimization affects both simulation and code generation.

  • When converting from floating point to fixed point, if the net slope is not a power of two, slope correction using division improves precision. For some processors, use of multiplication improves code efficiency.

Dependencies

  • This parameter requires a Fixed-Point Designer license.

Command-Line Information

Parameter: UseFloatMulNetSlope
Type: string
Value: 'on' | 'off'
Default: 'off'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn (when target hardware supports efficient multiplication)
Off (otherwise)
Safety precautionOff

See Also

Default for underspecified data type

Specify the default data type to use for inherited data types if Simulink software could not infer the data type of a signal during data type propagation.

Settings

Default: double

double

Sets the data type for underspecified data types during data type propagation to double. Simulink uses double as the data type for inherited data types.

single

Sets the data type for underspecified data types during data type propagation to single. Simulink uses single as the data type for inherited data types.

Tips

  • This setting affects both simulation and code generation.

  • For embedded designs that target single-precision processors, set this parameter to single to avoid the introduction of double data types.

  • Use the Model Advisor Identify questionable operations for strict single-precision design check to identify the double-precision usage in your model.

Command-Line Information

Parameter: DefaultUnderspecifiedDataType
Type: string
Value: 'double' | 'single'
Default: 'double'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
Efficiency On (when target hardware supports efficient single computations)
Off (otherwise)
Safety precautionNo impact

See Also

Optimize using the specified minimum and maximum values

Optimize generated code using the specified minimum and maximum values for signals and parameters in the model.

Settings

Default: Off

On

Optimizes the generated code using range information derived from the minimum and maximum specified values for signals and parameters in the model.

Off

Ignores specified minimum and maximum values when generating code.

Tips

  • Before generating code, test the specified values by simulating your model with simulation range checking enabled using the Diagnostics > Data Validity > Simulation range checking configuration parameter. If errors or warnings occur, fix these issues before generating code. Otherwise, optimization might result in numerical mismatch with simulation.

  • Specify minimum and maximum values for signals and parameters in the model for:

    • Inport and Outport blocks.

    • Block outputs.

    • Block inputs, for example, for the MATLAB Function and Stateflow Chart blocks.

    • Simulink.Signal objects.

  • This optimization does not take into account minimum and maximum values specified for:

    • Merge block inputs. To work around this, use a Simulink.Signal object on the Merge block output and specify the range on this object

    • Bus elements.

    • Conditionally-executed subsystem (such as a triggered subsystem) block outputs that are directly connected to an Outport block.

      Outport blocks in conditionally-executed subsystems can have an initial value specified for use only when the system is not triggered. In this case, the optimization cannot use the range of the block output because the range might not cover the initial value of the block.

  • If you use the Polyspace® Code Prover™software to verify code generated using this optimization, it might mark code that was previously green as orange. For example, if your model contains a division where the range of the denominator does not include zero, the generated code does not include protection against division by zero. Polyspace Code Prover might mark this code orange because it does not have information about the minimum and maximum values specified for the inputs to the division.

    The Polyspace Code Prover software does automatically capture some minimum and maximum values specified in the MATLAB® workspace, for example, for Simulink.Signal and Simulink.Parameter objects. In this example, to provide range information to the Polyspace Code Prover software, use a Simulink.Signal object on the input of the division and specify a range that does not include zero.

    The Polyspace Code Prover software stores these values in a Data Range Specification (DRS) file. However, they do not capture all minimum and maximum values specified in your Simulink model. To provide additional min/max information to Polyspace Code Prover, you can manually define a DRS file. For more information, see the Polyspace Code Prover documentation.

  • If you are using double-precision data types and the Code Generation > Interface > Support non-finite numbers configuration parameter is selected, this optimization does not occur.

  • If your model contains multiple instances of a reusable subsystem and each instance uses input signals with different specified minimum and maximum values, this optimization might result in different generated code for each subsystem so code reuse does not occur. Without this optimization, the Simulink Coder software generates code once for the subsystem and shares this code among the multiple instances of the subsystem.

  • The Model Advisor Check safety-related optimization settings check generates a warning if this option is selected. For many safety critical applications, it is not acceptable to remove dead code automatically because this might result in requirements without traceable code. For more information, see Check safety-related optimization settings.

  • Enabling this optimization improves the ability of the Fixed-Point Designer software to eliminate unnecessary utility functions and saturation code from the generated code.

Dependencies

  • This parameter appears for ERT-based targets only.

  • This parameter requires a Embedded Coder license when generating code.

Command-Line Information

Parameter: UseSpecifiedMinMax
Type: string
Value: 'on' | 'off'
Default: 'off'

Recommended Settings

ApplicationSetting
DebuggingOff
TraceabilityOff
EfficiencyOn
Safety precautionOff

See Also

Remove root level I/O zero initialization

Specify whether to generate initialization code for root-level inports and outports set to zero.

Settings

Default: Off (GUI), 'on' (command-line)

On

Does not generate initialization code for root-level inports and outports set to zero.

Off

Generates initialization code for all root-level inports and outports. Use the default:

  • To initialize memory allocated for C MEX S-function wrappers to zero.

  • To initialize all internal and external data to zero.

    Note:   Generated code never initializes data of ImportedExtern or ImportedExternPointer storage classes, regardless of configuration parameter settings.

Dependencies

  • This parameter appears only for ERT-based targets.

  • This parameter requires a Embedded Coder license when generating code.

Command-Line Information

Parameter: ZeroExternalMemoryAtStartup
Type: string
Value: 'off' | 'on'
Default: 'on'

    Note:   The command-line values are reverse of the settings values. Therefore, 'on' in the command line corresponds to the description of "Off" in the settings section, and 'off' in the command line corresponds to the description of "On" in the settings section.

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn (GUI), off (command line) (execution, ROM), No impact (RAM)
Safety precautionOff (GUI), on (command line)

See Also

Use memset to initialize floats and doubles to 0.0

Specify whether to generate code that explicitly initializes floating-point data to 0.0.

Settings

Default: On (GUI), 'off' (command-line)

On

Uses memset to clear internal storage for floating-point data to integer bit pattern 0 (all bits 0), regardless of type. An example of a case for selecting this option is to gain compiler efficiency when the compiler and target CPU both represent floating-point zero with the integer bit pattern 0.

Off

Generates code to explicitly initialize storage for data of types float and double to 0.0. The resulting code is slightly less efficient than code generated when you select the option.

You should not select this option if you need to ensure that memory allocated for C MEX S-function wrappers is initialized to zero.

Dependency

This parameter requires a Simulink Coder license.

Command-Line Information

Parameter: InitFltsAndDblsToZero
Type: string
Value: 'on' | 'off'
Default: 'off'

    Note:   The command-line values are reverse of the settings values. Therefore, 'on' in the command line corresponds to the description of "Off" in the settings section, and 'off' in the command line corresponds to the description of "On" in the settings section.

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn (GUI), 'off' (command-line) (execution, ROM), No impact (RAM)
Safety precautionNo impact

See Also

Remove internal data zero initialization

Specify whether to generate initialization code for internal work structures, such as block states and block outputs, to zero.

Settings

Default: Off (GUI), 'on' (command-line)

On

Does not generate code that initializes internal work structures to zero. An example of when you might select this parameter is to test the behavior of a design during warm boot—a restart without full system reinitialization.

Selecting this parameter does not guarantee that memory is in a known state each time the generated code begins execution. When you run a model or generated S-function multiple times, each run can produce a different answer, even when calling the model initialization function in an attempt to reset memory.

If want to get the same answer on every run from a generated S-function, enter the command clear SFcnNam or clear mex in the MATLAB Command Window before each run.

Off

Generates code that initializes internal work structures to zero. You should use the default:

  • To ensure that memory allocated for C MEX S-function wrappers is initialized to zero

  • For safety critical applications that require that all internal and external data be initialized to zero

Dependencies

  • This parameter appears only for ERT-based targets.

  • This parameter requires a Embedded Coder license when generating code.

Command-Line Information

Parameter: ZeroInternalMemoryAtStartup
Type: string
Value: 'off' | 'on'
Default: 'on'

    Note:   The command-line values are reverse of the settings values. Therefore, 'on' in the command line corresponds to the description of "Off" in the settings section, and 'off' in the command line corresponds to the description of "On" in the settings section.

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn (GUI), off (command line), (execution, ROM), No impact (RAM)
Safety precautionOff (GUI), on (command line)

See Also

Optimize initialization code for model reference

Specify whether to generate initialization code for blocks that have states.

Settings

Default: on

On

Suppresses generation of initialization code for blocks that have states unless the blocks are in a system that can reset its states, such as an enabled subsystem. This results in more efficient code.

Off

Generates initialization code for all blocks that have states. Disable this option if the current model includes a subsystem that resets states, such as an enabled subsystem, and the model is referred to from another model with a Model block.

Tips

The following restrictions apply to using the Optimize initialization code for model reference parameter. However, these restrictions do not apply to a Model block that references a function-call model.

  • In a subsystem that resets states, do not include a Model block that references a model that has this parameter set to on. For example, in an enabled subsystem with the States when enabling block parameter set to reset, do not include a Model block that references a model that has the Optimize initialization code for model reference parameter set to on.

  • If you set the Optimize initialization code for model reference parameter to off in a model that includes a Model block that directly references a model, do not set the Optimize initialization code for model reference parameter for the referenced model to on.

Dependencies

  • This parameter appears only for ERT-based targets.

  • This parameter requires a Embedded Coder license when generating code.

Command-Line Information

Parameter: OptimizeModelRefInitCode
Type: string
Value: 'on' | 'off'
Default: 'on'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn (execution, ROM), No impact (RAM)
Safety precautionNo impact

See Also

Remove code from floating-point to integer conversions that wraps out-of-range values

Remove wrapping code that handles out-of-range floating-point to integer conversion results.

Settings

Default: Off

On

Removes code when out-of-range conversions occur. Select this check box if code efficiency is critical to your application and the following conditions are true for at least one block in the model:

  • Computing the outputs or parameters of a block involves converting floating-point data to integer or fixed-point data.

  • The Saturate on integer overflow check box is cleared in the Block Parameters dialog box.

    Caution   Execution of generated code might not produce the same results as simulation.

Off

Results for simulation and execution of generated code match when out-of-range conversions occur. The generated code is larger than when you select this check box.

Tips

  • Selecting this check box reduces the size and increases the speed of the generated code at the cost of potentially producing results that do not match simulation in the case of out-of-range values.

  • Selecting this check box affects code generation results only for out-of-range values and cannot cause code generation results to differ from simulation results for in-range values.

Dependency

This parameter requires a Simulink Coder license.

Command-Line Information

Parameter: EfficientFloat2IntCast
Type: string
Value: 'on' | 'off'
Default: 'off'

Recommended Settings

ApplicationSetting
DebuggingOff
TraceabilityOff
EfficiencyOn (execution, ROM), No impact (RAM)
Safety precautionOff (for simulation and during development)
On (for production code generation)

See Also

Remove code from floating-point to integer conversions with saturation that maps NaN to zero

Remove code that handles floating-point to integer conversion results for NaN values.

Settings

Default: On

On

Removes code when mapping from NaN to integer zero occurs. Select this check box if code efficiency is critical to your application and the following conditions are true for at least one block in the model:

  • Computing outputs or parameters of a block involves converting floating-point data to integer or fixed-point data.

  • The Saturate on integer overflow check box is selected in the Block Parameters dialog box.

    Caution   Execution of generated code might not produce the same results as simulation.

Off

Results for simulation and execution of generated code match when mapping from NaN to integer zero occurs. The generated code is larger than when you select this check box.

Tips

  • Selecting this check box reduces the size and increases the speed of the generated code at the cost of producing results that do not match simulation in the case of NaN values.

  • Selecting this check box affects code generation results only for NaN values and cannot cause code generation results to differ from simulation results for any other values.

Dependencies

  • This parameter requires a Simulink Coder license.

  • For ERT-based targets, this parameter is enabled when you select the floating-point numbers and non-finite numbers check boxes in the Code Generation > Interface pane.

Command-Line Information

Parameter: EfficientMapNaN2IntZero
Type: string
Value: 'on' | 'off'
Default: 'on'

Recommended Settings

ApplicationSetting
DebuggingOff
TraceabilityOff
EfficiencyOn
Safety precautionOff (for simulation and during development)
On (for production code generation)

See Also

Remove code that protects against division arithmetic exceptions

Specify whether to generate code that guards against division by zero for fixed-point data.

Settings

Default: On

On

Does not generate code that guards against division by zero for fixed-point data. When you select this option, simulation results and results from generated code might not be in bit-for-bit agreement.

Off

Generates code that guards against division by zero for fixed-point data.

Dependencies

  • This parameter appears only for ERT-based targets.

  • This parameter requires a Embedded Coder license when generating code.

Command-Line Information

Parameter: NoFixptDivByZeroProtection
Type: string
Value: 'on' | 'off'
Default: 'on'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyOn
Safety precautionOff

See Also

Compiler optimization level

Sets the degree of optimization used by the compiler when generating code for acceleration.

Settings

Default: Optimizations off (faster builds)

Optimizations off (faster builds)

Specifies the compiler not to optimize code. This results in faster build times.

Optimizations on (faster runs)

Specifies the compiler to generate optimized code. The generated code will run faster, but the model build will take longer than if optimizations are off.

Tips

  • The default Optimizations off is a good choice for most models. This quickly produces code that can be used with acceleration.

  • Set Optimizations on to optimize your code. The fast running code produced by optimization can be advantageous if you will repeatedly run your model with the accelerator.

Command-Line Information

Parameter: SimCompilerOptimization
Type: string
Value: 'on' | 'off'
Default: 'off'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionNo impact

See Also

Verbose accelerator builds

Select the amount of information displayed during code generation for Simulink Accelerator mode, referenced model Accelerator mode, and Rapid Accelerator mode.

Settings

Default: Off

Off

Display limited amount of information during the code generation process.

On

Display progress information during code generation, and show the compiler options in use.

Command-Line Information

Parameter: AccelVerboseBuild
Type: string
Value: 'on' | 'off'
Default: 'off'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionNo impact

See Also

For more information about AccelVerboseBuild, see Controlling Verbosity During Code Generation.

Was this topic helpful?