# Non-virtual subsystems in ADM_Integrated_Logic

### 1. Code Mappings [hide]

This table: provides a mapping from non-virtual subsystems in model to functions or reusable functions in generated code. The table notes exceptions that caused nonvirtual subsystems to not reuse code even though they were assigned a function packaging setting ('Function packaging' entry on the Subsystem Block Dialog) of 'Auto' or 'Reusable function'.
Subsystem | Reuse Setting | Reuse Outcome | Outcome Diagnostic
--- | --- | --- | ---
<S49> | Auto | Reusable Function(S49) | normal
<S50> | Auto | Reusable Function(S49) | normal
<S9> | Auto | Reusable Function(S9) | normal
<S11> | Auto | Reusable Function(S9) | normal
<S10> | Auto | Reusable Function(S10) | normal
<S12> | Auto | Reusable Function(S10) | normal
<S17> | Auto | Inline | normal
<S19> | Auto | Inline | normal
<S20> | Auto | Inline | normal
<S22> | Auto | Inline | normal
<S4> | Auto | Inline | normal
<S5> | Auto | Inline | normal
<S6> | Auto | Inline | normal
<S37> | Auto | Inline | normal
<S38> | Auto | Inline | normal
<S39> | Auto | Inline | normal
<S48> | Auto | Inline | normal
<S45> | Auto | Inline | normal
<S56> | 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 non-reusable function without arguments, or 'Reusable function' to become a non-reusable 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 the differences in the functional attributes of the subsystems in the model or in the inlined generated code.
No reuse exception in model.