|
timemory 3.3.0
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.
|
#include "timemory/general/source_location.hpp"#include "timemory/mpl/apply.hpp"#include "timemory/mpl/filters.hpp"#include "timemory/operations/types.hpp"#include "timemory/utility/macros.hpp"#include "timemory/utility/transient_function.hpp"#include "timemory/variadic/base_bundle.hpp"#include "timemory/variadic/types.hpp"#include <cstdint>#include <cstdio>#include <fstream>#include <functional>#include <iomanip>#include <ios>#include <iostream>#include <string>#include "timemory/variadic/bundle.cpp"
Include dependency graph for bundle.hpp:
This graph shows which files directly or indirectly include this file:Go to the source code of this file.
Classes | |
| class | tim::bundle< Tag, BundleT, TupleT > |
Example: bundle<Tag, component_bundle<Foo>, mixed_wrapper_types<concat<Bar, Baz>>> will use Tag + trait::is_available<Tag> or trait::runtime_available<Tag> to disable this bundle at compile-time or run-time, respectively. It will covert component_bundle<Foo> to component_bundle<Foo, Bar, Baz> for purposes of function signatures and it will instantiate std::tuple<...> depending on the compile-time availability of Bar and Baz. mixed_wrapper_types is a dummy type with the appropriate aliases to perform these conversions. Here is a theoretical implementation of mixed_wrapper_types (which supports allocating components on the stack and the heap): More... | |
Namespaces | |
| namespace | tim |