Nonvirtual subsystems in ADM_Integrated_Logic

1. Code Mappings [hide]

This table:

  • Provides a mapping from nonvirtual subsystems in model to functions in generated code.
  • Notes exceptions that caused nonvirtual subsystems to not reuse code even though subsystem block parameter 'Function packaging' is set to 'Auto' or 'Reusable function'.

Subsystem Reuse Setting Reuse Outcome Outcome Diagnostic
<S68> Auto Reusable Function(S68) normal
<S69> Auto Reusable Function(S68) normal
<S15> Auto Reusable Function(S15) normal
<S19> Auto Reusable Function(S15) normal
<S16> Auto Reusable Function(S16) normal
<S20> Auto Reusable Function(S16) normal
<S26> Auto Inline normal
<S32> Auto Inline normal
<S29> Auto Inline normal
<S30> Auto Inline normal
<S4> Auto Inline normal
<S34> Auto Inline normal
<S36> Auto Inline normal
<S37> Auto Inline normal
<S39> Auto Inline normal
<S7> Auto Inline normal
<S8> Auto Inline normal
<S53> Auto Inline normal
<S9> Auto Inline normal
<S55> Auto Inline normal
<S56> Auto Inline normal
<S58> Auto Inline normal
<S67> Auto Inline normal
<S64> Auto Inline normal
<S12> Auto Inline normal
<S14> Auto Inline normal
<S17> Auto Inline normal
<S18> Auto Inline normal
<S21> Auto Inline normal
<S22> Auto Inline normal
<S75> Auto Inline normal

2. Code Reuse Exceptions [hide]

This section provides details on each exception that caused a nonvirtual subsystem with a function packaging setting of

  • 'Auto' to become an inlined code segment.
  • 'Auto' to become a nonreusable function without arguments.
  • 'Reusable function' to become a nonreusable function without arguments.
Note:This section does not report graphically identical nonvirtual subsystems marked as 'Auto' that were not reused due to differences in their functional properties (such as, dimensions, data types, work vectors, parameters, and so on). You can identify reasons for nonreuse in such cases by inspecting differences in functional attributes of subsystems in the model or in the inlined generated code.


No reuse exception in model.