Working with Compilation Reports

About Compilation Reports

Embedded MATLAB Coder produces reports in HTML format at compile time to help you debug your M-code and verify compliance with the Embedded MATLAB subset.

Back to Top

Generating Compilation Reports

Embedded MATLAB Coder automatically produces a compilation report if it detects errors or warnings.

You can also use the option to request reports even when there are no errors or warnings.

The report provides links to your M-code and C code files. It also provides compile-time type information for the variables and expressions in your M-code. This information simplifies finding sources of error messages and aids understanding of type propagation rules.

For example, to generate an embeddable C library for the file demo.m with a compilation report using emlc, at the MATLAB command line, enter:

emlc -T rtw:lib -report demo

Back to Top

Names and Locations of Compilation Reports

Embedded MATLAB Coder produces compilation reports in the following locations. The top-level html file at each location is index.html.

• For C MEX targets (mex):

  output_folder/mexfcn/primary_function_name/html

• For C executable targets (rtw:exe):

  output_folder/rtwexe/primary_function_name/html

• For C library targets (rtw:lib):

  output_folder/rtwlib/primary_function_name/html

Note   The default output folder is emcprj, but you can specify a different folder with the -d option (see emlc in the Real-Time Workshop reference documentation).

Back to Top

Opening Compilation Reports

To open the compilation report if no compilation errors occurred, click the Open compilation report link in the MATLAB Command Window.

To open the error report if compilation errors occurred, click the Open error report link in the MATLAB Command Window.

Back to Top

Description of Compilation Reports

When you compile M-files with the -report option, Embedded MATLAB Coder generates an HTML report. The following example shows a report for a successful compilation.

The report provides the following information, as applicable:

• M-code information, including a list of all functions and their compilation status

• Call stack information, providing information on the nesting of function calls

• Links to generated C code files

• Summary of compilation results, including type of target and number of warnings or errors

• List of all error and warning messages

• List of all variables in your M-code

• Target build log that records compilation and linking activities

Back to Top

Viewing Your M-Code

To view your M-code, click on the M-code tab. The compilation report displays the M-code for the function highlighted in the list on this tab.

The M-code tab provides:

• A list of the M-functions that have been compiled. The report displays icons next to each function name to indicate whether compilation was successful:

  • Errors in function.

  • Warnings in function.

  • Successful compilation, no errors or warnings.

• A filter control, Filter function list by attributes, that you can use to sort your functions by:

  • Size

  • Complexity

  • Class

Viewing Subfunctions

The compilation report annotates the subfunction with the name of the parent function in the list of functions on the M-code tab.

For example, if the M-functions fcn1 contains the subfunction subfcn and fcn2 contains the subfunction subfcn2, the report displays:

fcn1 > subfcn1
fcn2 > subfcn2

Viewing Specializations

If your Embedded MATLAB function calls the same function with different types of inputs, the compilation report numbers each of these specializations in the list of functions on the M-code tab.

For example, if the function fcn calls the function subfcn with different types of inputs:

function y = fcn(u) %#eml
% Specializations
y = y + subfcn(single(u));
y = y + subfcn(double(u));

The compilation report numbers the specializations in the list of functions.

fcn > subfcn > 1
fcn > subfcn > 2

Back to Top

Viewing Call Stack Information

To view call stack information, click the Call stack tab. The call stack lists the functions in the order that the top-level function calls them. It also lists the subfunctions that each function calls.

Back to Top

Viewing the Generated C Code

To view a list of the generated C files, click the C-code tab. The compilation report displays a list of the generated files. Click a file in the list to view the code in the code pane.

Navigating to C Code Source Files

When viewing C code in the code pane, click the blue link to the source file at the top of the pane to open the associated source code file in the MATLAB editor.

Viewing Type Definitions

The compilation report provides links to the definitions of data types. When viewing C code in the code pane, click the blue link for a data type to see its definition.

Back to Top

Viewing the Compilation Summary Information

To view a summary of the compilation results, including type of target and number of errors or warnings, click the Summary tab.

Back to Top

Viewing Error and Warning Messages

Embedded MATLAB Coder automatically reports errors and warnings. If errors occur during compilation, Embedded MATLAB Coder does not generate code. The report lists the messages in the order that the compiler detects them. It is best practice to address the first message in the list, because often subsequent errors and warnings are related to the first message. If compilation produces warnings, but no errors, Embedded MATLAB Coder does generate code.

The compilation report provides information about errors and warnings by:

• Listing all errors and warnings in the All Messages tab. The report lists these messages in chronological order.

• Highlighting all errors and warnings in the M-code pane

Viewing Errors and Warnings in the All Messages Tab

If errors or warnings occurred during compilation, click the All Messages tab to view a complete list of these messages. The compilation report marks messages as follows:

	Error
	Warning

To locate the offending line of code for an error or warning in the list, click the message in the list. The compilation report highlights errors in the list and M-code in red and warnings in orange. Click the blue line number next to the offending line of code in the M-code window to go to the error in the source file.

Note   You can only fix errors in the source file.

Viewing Error and Warning Information in Your M-Code

If errors or warnings occurred during compilation, the compilation report highlights them in your M-code.

To learn more about a particular error or warning, place your pointer over the highlighted text. The compilation report provides more information as follows:

• The report highlights errors in red and provides an error message.

  

  You can click the error to go to the message in the All Messages tab.

• The report highlights warnings in orange and provides a warning message.

  

  You can click the warning to go to the message in the All Messages tab.

Back to Top

Viewing Variables in Your M-Code

The compilation report provides compile-time type information for the variables and expressions in your M-code, including name, type, size, complexity, and class. The report also provides type information for fixed-point data types including word length and fraction length. You can use this type information to find sources of error messages and to understand type propagation rules.

You can view information about the variables in your M-code by:

• Viewing the list in the Variables tab

• Placing your pointer over the variable name in your M-code

Viewing Variables in the Variables Tab

To view a list of all the variables in your M-function, click the Variables tab. The compilation report displays a complete list of variables in the order they appear in the M-function selected in the M-code tab. Clicking a variable in the list highlights all instances of that variable, and scrolls the M-code panel so that the first instance is in view.

Tip   You can sort the variables by clicking the column headings in the Variables tab. To sort the variables by multiple columns, hold down the Shift key when clicking the column headings.

The report provides the following information about each variable, as applicable. The report only displays a column if at least one variable in the code has information in that column. For example, if the code does not contain any fixed-point data types, the report does not display the DT mode, WL or FL columns.

• Name

• Type

• Size

• Complexity

• Class

• DataTypeMode (DT mode) — for fixed-point data types only. For more information, see DataTypeMode in the Fixed-Point Toolbox documentation.

• Signed — sign information for built-in data types, signedness information for fixed-point data types

• Word length (WL) — for fixed-point data types only

• Fraction length (FL) — for fixed-point data types only

Viewing Information about Variable-Size Arrays in the Variables Tab.   For variable-size arrays, the size field includes information on the computed maximum size of the array. The size of each array dimension that varies is prefixed with a colon :.

If Embedded MATLAB technology cannot compute the maximum size of a variable-sized array, the compilation report displays the size as :?.

For more information on how to use the size information for variable-sized arrays, see Representing Data that Varies in Size at Runtime in the Embedded MATLAB documentation.

Viewing Information about Variables and Expressions in Your Embedded MATLAB Function Code

To view information about a particular variable or expression in your Embedded MATLAB function code, place your pointer over the variable name or expression in the M-code pane. The compilation report highlights variables and expressions in different colors.

Green, when the variable has data type information at this location in the code.  

For variable-sized arrays, the size field includes information on the computed maximum size of the array. The size of each array dimension that varies is prefixed with a colon :.

Pink, when the variable has no data type information.  

Purple, information about expressions.   You can also view information about expressions in your M-code. Place your pointer over an expression in the M-code pane. The compilation report highlights expressions in purple and provides more detailed information.

Red, when there is error information for an expression.   If the Embedded MATLAB software cannot compute the maximum size of a variable-sized array, the compilation report provides error information.

Back to Top

Viewing Target Build Information

If Embedded MATLAB Coder compiles your M-code without errors, it provides target build information in the Target Build Log tab, including:

• Build folder

  Clicking this link changes the MATLAB current folder to the build folder.

• Make wrapper

  The name of the batch file that Embedded MATLAB Coder used for this build.

• Build log

Back to Top

Keyboard Shortcuts for the Compilation Report

You can use the following keyboard shortcuts to navigate between the different panes in the compilation report. Once you have selected a pane, use the Tab key to advance through data in that pane.

Back to Top

Embedded MATLAB Coder Compilation Report Limitations

The compilation report displays information about the variables and expressions in your M-code with the following limitations:

 varargin and varargout

 Loop Unrolling

 Dead Code

 Structures

 Column Headings on Variables Tab

 Comments

 Multiline Matrices

out1 = [1 2 3; 
       4 5 6];

out1 = [1 2 3; 4 5 6];

Back to Top

How emlc Generates Code

Calling Generated C Functions

Related Products & Applications

• Simulink
• Control Design
• Signal Processing & Communications
• Model-Based Design
• Physical Modeling
• Verification & Validation

Get Simulink trial software

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

Get this Simulink Kit