-
Notifications
You must be signed in to change notification settings - Fork 20
SimSYCL is now thread-safe; remove workarounds #318
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
Conversation
Check-perf-impact results: (000e2892abb21ddd1ae413a5c86d7d95) ❓ No new benchmark data submitted. ❓ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clang-Tidy
found issue(s) with the introduced code (1/1)
a0440f8
to
539b74b
Compare
Pull Request Test Coverage Report for Build 12787716791Details
💛 - Coveralls |
539b74b
to
9184c35
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clang-Tidy
found issue(s) with the introduced code (1/1)
9184c35
to
3fd21c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clang-Tidy
found issue(s) with the introduced code (1/1)
3fd21c8
to
eeff793
Compare
Check-perf-impact results: (c8fb992b35322012b54e351345fdf71a) ❓ No new benchmark data submitted. ❓ |
Since celerity/SimSYCL#14 is now merged, we don't need explicit threading workarounds in the backend anymore.