From e3a59e2e91e628a289b74174f3adc4e133855dfa Mon Sep 17 00:00:00 2001 From: Sanjay Patel Date: Tue, 10 Apr 2018 17:56:24 +0000 Subject: [PATCH] [llvm-mca] fix formatting llvm-svn: 329729 --- llvm/docs/CommandGuide/llvm-mca.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/llvm/docs/CommandGuide/llvm-mca.rst b/llvm/docs/CommandGuide/llvm-mca.rst index d697511f9d8d..039130768660 100644 --- a/llvm/docs/CommandGuide/llvm-mca.rst +++ b/llvm/docs/CommandGuide/llvm-mca.rst @@ -41,20 +41,20 @@ assembly text: .. code-block:: c++ -int foo(int a, int b) { - __asm volatile("# LLVM-MCA-BEGIN foo"); - a += 42; - __asm volatile("# LLVM-MCA-END"); - a *= b; - return a; -} + int foo(int a, int b) { + __asm volatile("# LLVM-MCA-BEGIN foo"); + a += 42; + __asm volatile("# LLVM-MCA-END"); + a *= b; + return a; + } So for example, you can compile code with clang, output assembly, and pipe it directly into llvm-mca for analysis: .. code-block:: bash -$ clang foo.cpp -O2 -target x86_64-unknown-unknown -S -o - | llvm-mca -mcpu=btver2 + $ clang foo.cpp -O2 -target x86_64-unknown-unknown -S -o - | llvm-mca -mcpu=btver2 Multiple regions can be specified provided that they do not overlap. A code region can have an optional description. If no user defined region is specified,