when run on the target, but also help with diagnosing potential performance
issues.
-Given an assembly code sequence, llvm-mca estimates the IPC, as well as
-hardware resource pressure. The analysis and reporting style were inspired by
-the IACA tool from Intel.
+Given an assembly code sequence, llvm-mca estimates the Instructions Per Cycle
+(IPC), as well as hardware resource pressure. The analysis and reporting style
+were inspired by the IACA tool from Intel.
:program:`llvm-mca` allows the usage of special code comments to mark regions of
the assembly code to be analyzed. A comment starting with substring
The report is structured in three main sections. The first section collects a
few performance numbers; the goal of this section is to give a very quick
overview of the performance throughput. In this example, the two important
-performance indicators are the predicted total number of cycles, and the
-Instructions Per Cycle (IPC). IPC is probably the most important throughput
-indicator. A big delta between the Dispatch Width and the computed IPC is an
-indicator of potential performance issues.
+performance indicators are the predicted total number of cycles, and the IPC.
+IPC is probably the most important throughput indicator. A big delta between
+the Dispatch Width and the computed IPC is an indicator of potential
+performance issues.
The second section of the report shows the latency and reciprocal
throughput of every instruction in the sequence. That section also reports