Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix group barrier execution scope after sub-group feature is added #1343

Open
adarshyoga opened this issue Feb 16, 2024 · 0 comments
Open

Fix group barrier execution scope after sub-group feature is added #1343

adarshyoga opened this issue Feb 16, 2024 · 0 comments

Comments

@adarshyoga
Copy link
Contributor

The execution scope of group_barrier needs to be determined based on the group argument. Currently it is hard-coded to MemoryScope.WORK_GROUP since numba-dpex only supports group_barrier on work groups. Once sub-groups are added, then group_barrier can be called on both work groups and sub-groups.

The following changes need to performed once sub-group feature is added.

If group refers to a work_group then, execution scope needs to be set to MemoryScope.WORK_GROUP.
If group refers to a sub-group then, execution scope needs to be set to MemoryScope.SUB_GROUP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant