| Name: target exit data | Association: none |
| Category: executable | Properties: parallelism-generating, task-generating, device, device-affecting, data-mapping, map-exiting, mapping-only |
|
|
Clauses
depend, device, if, map, nowaitBinding
The binding task set for a target exit data region is the generating task, which is the target task generated by the target exit data construct. The target exit data region binds to the corresponding target task region.Semantics
When a target exit data construct is encountered, the list items in the map clauses are unmapped from the device data environment according to the map clause semantics. The target exit data construct generates a target task. The generated task region encloses the target exit data region. If a depend clause is present, it is associated with the target task. If the nowait clause is present, execution of the target task may be deferred. If the nowait clause is not present, the target task is an included task.All clauses are evaluated when the target exit data construct is encountered. The data environment of the target task is created according to the data-mapping attribute clauses on the target exit data construct, per-data environment ICVs, and any default data-sharing attribute rules that apply to the target exit data construct. If a variable or part of a variable is mapped by the target exit data construct, the variable has a default data-sharing attribute of shared in the data environment of the target task.
Assignment operations associated with mapping a variable (see Section 5.8.3) occur when the target task executes.
When an if clause is present and the if clause expression evaluates to false, the target device is the host.
Execution Model Events
Events associated with a target task are the same as for the task construct defined in Section 12.5.
The target-exit-data-begin event occurs after creation of the target task and completion of all predecessor tasks that are not target tasks for the same device. The target-exit-data-begin event is a target-task-begin event.
The target-exit-data-end event occurs after all other events associated with the target exit data construct.
Tool Callbacks
Callbacks associated with events for target tasks are the same as for the task construct defined in Section 12.5; (flags & ompt_task_target) always evaluates to true in the dispatched callback.
A thread dispatches a registered ompt_callback_target or ompt_callback_target_emi callback with ompt_scope_begin as its endpoint argument and ompt_target_exit_data or ompt_target_exit_data_nowait if the nowait clause is present as its kind argument for each occurrence of a target-exit-data-begin event in that thread in the context of the target task on the host. Similarly, a thread dispatches a registered ompt_callback_target or ompt_callback_target_emi callback with ompt_scope_end as its endpoint argument and ompt_target_exit_data or ompt_target_exit_data_nowait if the nowait clause is present as its kind argument for each occurrence of a target-exit-data-end event in that thread in the context of the target task on the host. These callbacks have type signature ompt_callback_target_t or ompt_callback_target_emi_t, respectively.
Restrictions
Restrictions to the target exit data construct are as follows:Cross References