Prev

Next

Index-> contents reference index search external

Up-> CppAD AD ADValued atomic atomic_base atomic_base_clear

ADValued-> Arithmetic unary_standard_math binary_math CondExp Discrete numeric_limits atomic

atomic-> checkpoint atomic_base

atomic_base-> atomic_ctor atomic_option atomic_afun atomic_forward atomic_reverse atomic_for_sparse_jac atomic_rev_sparse_jac atomic_for_sparse_hes atomic_rev_sparse_hes atomic_base_clear atomic_get_started.cpp atomic_norm_sq.cpp atomic_reciprocal.cpp atomic_set_sparsity.cpp atomic_tangent.cpp atomic_eigen_mat_mul.cpp atomic_eigen_mat_inv.cpp atomic_eigen_cholesky.cpp atomic_mat_mul.cpp

atomic_base_clear

Headings-> Syntax Purpose Future Use Restriction

@(@\newcommand{\W}[1]{ \; #1 \; } \newcommand{\R}[1]{ {\rm #1} } \newcommand{\B}[1]{ {\bf #1} } \newcommand{\D}[2]{ \frac{\partial #1}{\partial #2} } \newcommand{\DD}[3]{ \frac{\partial^2 #1}{\partial #2 \partial #3} } \newcommand{\Dpow}[2]{ \frac{\partial^{#1}}{\partial {#2}^{#1}} } \newcommand{\dpow}[2]{ \frac{ {\rm d}^{#1}}{{\rm d}\, {#2}^{#1}} }@)@ Free Static Variables
Syntax
atomic_base<Base>::clear()

Purpose
Each atomic_base objects holds onto work space in order to avoid repeated memory allocation calls and thereby increase speed (until it is deleted). If an the atomic_base object is global or static because, the it does not get deleted. This is a problem when using thread_alloc free_all to check that all allocated memory has been freed. Calling this clear function will free all the memory currently being held onto by the atomic_base<Base> class.

Future Use
If there is future use of an atomic_base object, after a call to clear, the work space will be reallocated and held onto.

Restriction
This routine cannot be called while in parallel execution mode.

---

Input File: cppad/core/atomic_base.hpp