HOME
| OPENMP API Specification: Version 5.1 November 2020

3.11.1  omp_fulfill_event

Summary This routine fulfills and destroys an OpenMP event.

Format

SVG-Viewer needed.

 

 
void omp_fulfill_event(omp_event_handle_t event);  

SVG-Viewer needed.

SVG-Viewer needed.

 

 
subroutine omp_fulfill_event(event) 
integer (kind=omp_event_handle_kind) event  

SVG-Viewer needed.

Constraints on Arguments A program that calls this routine on an event that was already fulfilled is non-conforming. A program that calls this routine with an event handle that was not created by the detach clause is non-conforming.

Effect The effect of this routine is to fulfill the event associated with the event handle argument. The effect of fulfilling the event will depend on how the event was created. The event is destroyed and cannot be accessed after calling this routine, and the event handle becomes unassociated with any event.

Execution Model Events The task-fulfill event occurs in a thread that executes an omp_fulfill_event region before the event is fulfilled if the OpenMP event object was created by a detach clause on a task.

Tool Callbacks A thread dispatches a registered ompt_callback_task_schedule callback with NULL as its next_task_data argument while the argument prior_task_data binds to the detached task for each occurrence of a task-fulfill event. If the task-fulfill event occurs before the detached task finished the execution of the associated structured-block, the callback has ompt_task_early_fulfill as its prior_task_status argument; otherwise the callback has ompt_task_late_fulfill as its prior_task_status argument. This callback has type signature ompt_callback_task_schedule_t.

Cross References

SVG-Viewer needed.