Main Content

Largest atomic size: integer

Largest integer data type supported for atomic loading and storage on test hardware

Model Configuration Pane: Hardware Implementation

Description

Specify the largest integer data type that can be atomically loaded and stored on the hardware that you use to test code. Use this parameter, where possible, to remove unnecessary double-buffering or unnecessary semaphore protection, based on data size, in generated multirate code.

Selecting a device by using the Device vendor and Device type parameters sets a device-specific value for this parameter.

Dependencies

This parameter is enabled only if you can modify it for the selected hardware.

Settings

Char (default) | Short | Int | Long | LongLong
Char

Specifies that char is the largest integer data type that can be atomically loaded and stored on the hardware that you use to test code.

Short

Specifies that short is the largest integer data type that can be atomically loaded and stored on the hardware that you use to test code.

Int

Specifies that int is the largest integer data type that can be atomically loaded and stored on the hardware that you use to test code.

Long

Specifies that long is the largest integer data type that can be atomically loaded and stored on the hardware that you use to test code.

LongLong

Specifies that long long is the largest integer data type that can be atomically loaded and stored on the hardware that you use to test code.

You can set this parameter value to LongLong only if the hardware used to test the code supports the C long long data type and you have selected Enable long long.

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyTarget specific
Safety precaution

No impact when Test hardware is the same as production hardware is selected. If it is not selected, no recommendation.

Programmatic Use

Parameter: TargetLargestAtomicInteger
Type: string | character vector
Values: 'Char' | 'Short' | 'Int' | 'Long' | 'LongLong'
Default: 'Char'

Version History

Introduced in R2010a