Loading...
Searching...
No Matches
Dirty variables are ones which have their address taken so we can't reliably work out where they may be assigned and are also considered shared state in the presence of multi-threading.
More...
#include <dirty.h>
+ Collaboration diagram for dirtyt:
Protected Member Functions
Detailed Description
Dirty variables are ones which have their address taken so we can't reliably work out where they may be assigned and are also considered shared state in the presence of multi-threading.
Definition at line 27 of file dirty.h.
Member Typedef Documentation
◆ goto_functiont
Constructor & Destructor Documentation
◆ dirtyt() [1/3]
dirtyt::dirtyt
(
)
inline
- Postcondition
- dirtyt objects that are created through this constructor are not safe to use. If you copied a dirtyt (for example, by adding an object that owns a dirtyt to a container and then copying it back out), you will need to re-initialize the dirtyt by calling dirtyt::build().
Definition at line 47 of file dirty.h.
◆ dirtyt() [2/3]
◆ dirtyt() [3/3]
Member Function Documentation
◆ add_function()
◆ build() [1/2]
◆ build() [2/2]
◆ die_if_uninitialized()
void dirtyt::die_if_uninitialized
(
)
const
inlineprivate
◆ find_dirty()
◆ find_dirty_address_of()
◆ get_dirty_ids()
const std::unordered_set<
irep_idt > & dirtyt::get_dirty_ids
(
)
const
inline
◆ operator()() [1/2]
◆ operator()() [2/2]
◆ output()
void dirtyt::output
(
std::ostream &
out )
const
◆ search_other()
Member Data Documentation
◆ dirty
std::unordered_set<
irep_idt> dirtyt::dirty
protected
◆ initialized
The documentation for this class was generated from the following files:
- /home/runner/work/cbmc/cbmc/src/analyses/dirty.h
- /home/runner/work/cbmc/cbmc/src/analyses/dirty.cpp