Lines Matching +refs:llvm +refs:mode

1 llvm-exegesis - LLVM Machine Instruction Benchmark
4 .. program:: llvm-exegesis
9 :program:`llvm-exegesis` [*options*]
14 :program:`llvm-exegesis` is a benchmarking tool that uses information available
18 Given an LLVM opcode name and a benchmarking mode, :program:`llvm-exegesis`
29 :program:`llvm-exegesis` can also benchmark arbitrary user-provided code
40     $ llvm-exegesis -mode=latency -opcode-name=ADD64rr
46     $ llvm-exegesis -mode=uops -opcode-name=ADD64rr
47     $ llvm-exegesis -mode=inverse_throughput -opcode-name=ADD64rr
58     mode:            latency
76     $ llvm-exegesis -mode=latency -opcode-index=-1
87     $ echo "vzeroupper" | llvm-exegesis -mode=uops -snippets-file=-
90 :program:`llvm-exegesis` checks the liveliness of registers (i.e. any register
94 - Mark the register as requiring a definition. :program:`llvm-exegesis` will
99 - Mark the register as a "live in". :program:`llvm-exegesis` will benchmark
124     $ llvm-exegesis -mode=analysis \
151 :program:`llvm-exegesis` will also analyze the clusters to point out
155 .. image:: llvm-exegesis-analysis.png
159 :program:`llvm-exegesis` is compiled in debug mode, else only the class id will
186 .. option:: -mode=[latency|uops|inverse_throughput|analysis]
188  Specify the run mode. Note that some modes have additional requirements and options.
190  `latency` mode can be  make use of either RDTSC or LBR.
192 …To run in `latency` mode, a positive value must be specified for `x86-lbr-sample-period` and `--re…
194  In `analysis` mode, you also need to specify at least one of the
200   When a positive value is specified for this option and when the mode is `latency`,
206 .. option:: -repetition-mode=[duplicate|loop|min]
208  Specify the repetition mode. `duplicate` will create a large, straight line
211  mode tends to better hide the effects of the CPU frontend on architectures
214  to instead use the `min` mode, which will run each other mode, and produce
229  `-max-configs-per-opcode` larger than `1` allows `llvm-exegesis` to explore
236  File to read (`analysis` mode) or write (`latency`/`uops`/`inverse_throughput`
259  (`analysis` mode, DBSCAN only).
264  (`analysis` mode).
269  is different from the LLVM schedule profile values (`analysis` mode).
289  By default, llvm-exegesis will dump the generated code to a temporary file to
296 :program:`llvm-exegesis` returns 0 on success. Otherwise, an error message is