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

Memory Barrier #2

Open
motters opened this issue Jun 12, 2018 · 0 comments
Open

Memory Barrier #2

motters opened this issue Jun 12, 2018 · 0 comments

Comments

@motters
Copy link
Contributor

motters commented Jun 12, 2018

When access memory / registers (virtual address) it would be nice if the driver classes applied a memory barrier.

This features should have the option to be disabled as it will add an overhead and is probably not required in most cases.

This can be done using "__sync_synchronize();" before and after reads / writes. However it should probably be wrapped up in a platform class or function.

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