timemory
3.2.1
Modular C++ Toolkit for Performance Analysis and Logging. Profiling API and Tools for C, C++, CUDA, Fortran, and Python. The C++ template API is essentially a framework to creating tools: it is designed to provide a unifying interface for recording various performance measurements alongside data logging and interfaces to other tools.
|
This is a variadic component wrapper where all components are allocated on the stack and cannot be disabled at runtime. This bundler has the lowest overhead. Accepts unlimited number of template parameters. This bundler is used by tim::auto_tuple whose constructor and destructor invoke the start() and stop() member functions respectively. More...
#include "timemory/variadic/component_tuple.hpp"
Public Types | |
using | captured_location_t = source_location::captured |
using | bundle_type = bundle< TIMEMORY_API, component_tuple<>, tim::variadic::stack_wrapper_types< concat< Types... > >> |
using | this_type = component_tuple< Types... > |
using | component_type = component_tuple< Types... > |
using | auto_type = auto_tuple< Types... > |
Public Member Functions | |
template<typename... Args> | |
component_tuple (Args &&...) | |
~component_tuple ()=default | |
component_tuple (const component_tuple &)=default | |
component_tuple (component_tuple &&) noexcept=default | |
component_tuple & | operator= (const component_tuple &rhs)=default |
component_tuple & | operator= (component_tuple &&) noexcept=default |
template<typename... Args> | |
component_tuple (Args &&... args) | |
This is a variadic component wrapper where all components are allocated on the stack and cannot be disabled at runtime. This bundler has the lowest overhead. Accepts unlimited number of template parameters. This bundler is used by tim::auto_tuple whose constructor and destructor invoke the start() and stop() member functions respectively.
Types | Specification of the component types to bundle together |
The above code will record wall-clock, cpu-clock, and peak-rss. The intermediate storage will happen on the stack and when the destructor is called, it will add itself to the call-graph
Definition at line 76 of file component_tuple.hpp.
using tim::component_tuple< Types >::auto_type = auto_tuple<Types...> |
Definition at line 88 of file component_tuple.hpp.
using tim::component_tuple< Types >::bundle_type = bundle<TIMEMORY_API, component_tuple<>, tim::variadic::stack_wrapper_types<concat<Types...> >> |
Definition at line 84 of file component_tuple.hpp.
using tim::component_tuple< Types >::captured_location_t = source_location::captured |
Definition at line 82 of file component_tuple.hpp.
using tim::component_tuple< Types >::component_type = component_tuple<Types...> |
Definition at line 87 of file component_tuple.hpp.
using tim::component_tuple< Types >::this_type = component_tuple<Types...> |
Definition at line 86 of file component_tuple.hpp.
tim::component_tuple< Types >::component_tuple | ( | Args && | ... | ) |
|
default |
|
default |
|
defaultnoexcept |
tim::component_tuple< Types >::component_tuple | ( | Args &&... | args | ) |
Definition at line 104 of file component_tuple.hpp.
|
defaultnoexcept |
|
default |