In generated code, a block's DWork vectors are usually set to zero in the initialization function. The set to zero operations are always done using a for loop even if the widths of the DWork vectors are less than the specified roll threshold.
MATLAB: Is there an inefficient loop generated in the initialization function of generated code in Real-Time Workshop 6.0 (R14)
dworkfunctioninitializationrollrtwsimulink coderthreshold
Related Question
- Is rtw_extmode.h included in the header file even if not using Real-Time Workshop in external mode for a model that uses model referencing in Simulink 6.0 (R14)
- Do I receive a runtime error when I run the executable for a relatively large scale Simulink model generated using Real Time Workshop 6.0 (R14)
- Does Real-Time Workshop crash when code generation is performed on block diagrams with multibyte characters
- How to set the Parameter Pooling optimization in Real-Time Workshop 6.0 (R14)
- Does the Data Store Write block in the model seem to not update the destination memory when used with S-function Target in Real-Time Workshop
- How to copy all port names to the attached signal lines in Simulink 6.0 (R14)
- Does the custom TLC code not display the correct parameter values in Real-Time Workshop 6.1 (R14SP1)
- Do I receive different results in the generated code between Real-Time Workshop 6.0 (R14) and Real-Time Workshop 6.1 (R14SP1) and 6.0 (R14) when performing integer multiplication in the model
Best Answer