Lines Matching refs:can

15 instrumentation points and a runtime library that can dynamically enable and
18 More high level information about XRay can be found in the `XRay whitepaper`_.
45 You can use XRay in a couple of ways:
66 get XRay instrumentation points. You can tweak that number through the
73 The loop detection can be disabled with ``-fxray-ignore-loops`` to use only the
74 instruction threshold. You can also specifically instrument functions in your
76 You can do it using the GCC-style attributes or C++11-style attributes.
88 When linking a binary, you can either manually link in the `XRay Runtime
90 ``-fxray-instrument`` flag. Alternatively, you can statically link-in the XRay
98 If you're using LLVM IR directly, you can add the ``function-instrument``
112 You can also set the ``xray-instruction-threshold`` attribute and provide a
125 Attributes can be imbued through the use of special case files instead of
126 adding them to the original source files. You can use this to mark certain
140 These files can be provided through the ``-fxray-attr-list=`` flag to clang.
159 These options can be controlled through the ``XRAY_OPTIONS`` environment
192   ``__xray_log_register_mode(...)`` can be chosen with this function.
198 Once a logging implementation has been initialized, it can be "stopped" by
201 an implementation's data can be cleared out through the
214 execution, and periodically append to a single log. This mode can be
216 environment variable. Combined with ``patch_premain=true`` this can allow for
220 implementation can be configured through the ``__xray_log_init_mode(...)``
222 defaults can be provided in the ``XRAY_BASIC_OPTIONS`` environment variable.
234 implementation can be provided in the ``XRAY_FDR_OPTIONS`` environment
235 variable. Programmatic configuration can be done by calling
243 the logging implementation is finalized -- at which point it can be flushed and
281 We currently have the beginnings of a trace analysis tool in LLVM, which can be
290 - ``convert``: Converts an XRay log file from one format to another. We can
318 ``function-exit``, ``custom``, and ``typed`` points. These can be enabled individually
326 This will omit the other sled types entirely, reducing the binary size. You can also
335 different subset you can specify ``-fxray-selected-function-group=`` with a group number
355 - With a large instrumented binary, the size of generated XRay traces can