sync_strict

The sync_strict policy is used to create synchronous metrics. As the name suggests, such metrics are running synchronous to the actual instrumented application, i.e., the plugin is asked at every enter and leave event for a metric value.

The difference between the sync policy and the sync_strict policy is, that the sync_strict must provide a metric value, the sync can provide one.

This policy is mutually exclusive with the async policy and the sync policy.

Required methods

template <class Proxy> void get_current_value(std::int32_t id, Proxy& p)

This function gets called at every enter and leave event.

Arguments:

• id - the id returned to Score-p in add_counter() (See Base)
• p - the Proxy used to write data

Provided methods

This policy doesn't provide any methods.

See also

• sync
• synchronize
• object_id
• scorep_clock