Main Content

Verify Code Replacement Library

Verify your code replacement library by examining its structure, replacement, and performance. Use the Code Replacement Viewer (crviewer) to verify the structure of your library. Use the code replacement report to verify the replacements made with your library in generated code. Use crviewer again to verify the performance of your library during code generation by examining the replacement hit and miss logs.

Verify Library Structure

Use the Code Replacement Viewer (crviewer) to open and view the structure of your code replacement library by examining its tables and table entries.

  1. From the MATLAB® command window, open your code replacement library using the crviewer with the command:

  2. The viewer opens your code replacement library and shows its code replacement tables in the left pane. Verify that your library lists the required tables in the relative order.

  3. Open and view the entries for each code replacement table. In the crtool, click each table listed in the left pane to view its entries in the middle pane.

    If you are not using the crviewer, you can open each table directly from the MATLAB command prompt with the command:


  4. For each table in your library, verify that it lists the required entries in the relative order. Verify that the conceptual representation and implementation representation are correct for each entry in the table.

Verify Library Replacement

Use the Code Replacements Report to verify that when the code generator uses your code replacement library it creates replacements as expected in the generated code. For each instance of replacement, the Code Replacements Report provides a mapping between the Simulink block that triggered the replacement and its implementation in the generated code. Use this mapping to verify code replacement by tracing between the report and the code in either direction (from report to code or code to report).

To generate the Code Replacements Report:

  1. Configure your model to use your code replacement library.

  2. Configure your model to open the Code Generation Report. The Code Replacements Report is a tab within this report. In the Model Configuration Parameters dialog box, in the Code Generation > Report pane, select:

    • Create code generation report

    • Open report automatically

    • Model-to-code

    • Summarize which block triggered code replacements

  3. Configure the generated code to include comments. In the Model Configuration Parameters dialog box, in the Code Generation > Comments pane, select:

    • Include comments

    • Either or both of Simulink block comments and Simulink block descriptions

  4. Build your model to generate code only. The Code Generation Report opens automatically. On the left pane, click to open the Code Replacements Report.

  5. Verify that code replacements occur as expected.

    • Navigate from report to model: In the Code Replacements Report, click each block link to see the source that triggered replacement.

    • Navigate from model to report: In the Simulink model window, use model-to-code highlighting to trace code replacements. Right-click blocks where you expected code replacement to occur and select C/C++ Code > Navigate to C/C++ Code. The report appears with the corresponding replacement code highlighted.

Verify Library Performance

Verify the performance of your code replacement library by examining the hits and misses that occurred during code generation using your library. During code generation, when the code generator finds a match for code replacement from your code replacement library, it logs the hit in a hit cache. When it does not find a code replacement match, it logs the failed attempt in the miss cache. Each time that you generate code, the code generator overwrites its previous hit and miss cache logs.

To review trace information from the hit and miss cache data, use the Code Replacement Viewer (crviewer). From the hit cache, you can identify when code replacement occurred, and from the miss cache, you can troubleshoot when code replacement did not take place. The miss cache trace information provides you information about the reason for the miss, a link to the relevant source location for the miss, and the call site object of the miss. For more information, see Troubleshoot Code Replacement Misses.

Review Code Replacements

After you review the content of your code replacement library and tables, generate code and a code generation report. Verify that the code generator replaces code as you expect.

The Code Replacements Report details the code replacement library functions that the code generator uses for code replacements. The report provides a mapping between each replacement instance and the line of MATLAB code that triggered the replacement. The Code Replacements report is not available for generated MEX functions.

The following example illustrates two complementary approaches for reviewing code replacements:

  • Check the Code Replacements Report section of the code generation report for expected replacements.

  • Trace code replacements.

  1. Identify the MATLAB function where you anticipate that a function or operator replacement occurs. This example uses this function:

    function [y1, y2] = addsub_two_int16(u1, u2)
    y1 = int16(u1 + u2);
    y2 = int16(u1 - u2);

  2. Identify or create code or a script to exercise the function. For example, consider test file addsub_to_int16_test.m, which includes the following code:

    u1 = int16(10)
    u2 = int16(10)
    [y1, y2] = addsub_two_int16(u1, u2);
    disp('y1 =')
    disp('y2 =')
  3. Open the MATLAB Coder™ app.

  4. On the Select Source Files page, add your function to the project. For this example, add function addsub_two_int16. Click Next.

  5. On the Define Input Types page, use the test file addsub_to_int16_test to automatically define the input types. Click Next.

  6. On the Check for Run-Time Issues page, specify the test file addsub_to_int16_test. The app runs the test file, replacing calls to addsub_to_int16_test with calls to a MEX version of addsub_to_int16_test. Click Next.

  7. To open the Generate dialog box, on the Generate Code page, click the Generate arrow .

  8. Set Build type to generate source code. Before you build an executable, you want to review your code replacements in the generated code.

  9. In the Generate dialog box, click More Settings.

  10. Configure the code generator to use your code replacement library. On the Custom Code tab, set the Code replacement library parameter to the name of your library. For this example, set the library to Addition & Subtraction Examples.

  11. Configure the code generation report to include the Code Replacements Report. On the Debugging tab, select:

    • Always create a code generation report

    • Code replacements

    • Automatically launch a report if one is generated

  12. To generate code and a report, set Build type to Source Code. Then, click Generate.

  13. Open the Code Replacements Report section of the code generation report.

    That report lists the replacement functions that the code generator used. The report provides a mapping between each replacement instance and the MATLAB code that triggered the replacement.

    Review the report:

    • Check whether expected function and operator code replacements occurred.

    • In the replacements sections, click each code link to see the source that triggered the reported code replacement.

If a function or operator is not replaced as expected, the code generator used a higher-priority (lower-priority value) match or did not find a match.

To analyze and troubleshoot code replacement misses, use the trace information that the Code Replacement Viewer provides.

Related Topics