Main Content

ssFxpGetU32BitRegionCompliant

Determine whether S-function is compliant with the U32 bit region interface

The ssFxpGetU32BitRegionCompliant function can be ignored. This function no longer has any impact on the memory layout for inputs and outputs. The memory layout introduced in R2008a is always used.

Syntax

extern ssFxpSGetU32BitRegionCompliant(SimStruct *S,
                            int *result)

Arguments

S

SimStruct representing an S-function block.

result

  • 1 if S-function calls ssFxpSetU32BitRegionCompliant to declare compliance with memory footprint for fixed-point data types with 33 or more bits

  • 0 if S-function does not call ssFxpSetU32BitRegionCompliant

Description

Before R2020a: This function checks whether the S-function calls ssFxpSetU32BitRegionCompliant to declare compliance with the memory footprint for fixed-point data types with 33 or more bits. Before calling any other Fixed-Point Designer™ API function on data with 33 or more bits, you must call ssFxpSetU32BitRegionCompliant as follows:

ssFxpSetU32BitRegionCompliant(S,1);

Note

The Fixed-Point Designer software assumes that S-functions that use fixed-point data types with 33 or more bits without calling ssFxpSetU32BitRegionCompliant are using the memory footprint that existed until R2007b. Either redesign these S-functions or isolate them using the library fixpt_legacy_sfun_support.

Requirement

To use this function, you must include fixedpoint.h and fixedpoint.c. For more information, see Structure of the S-Function.

Languages

C

Version History

Introduced in R2009a