GlobalAtomicObject - Scalable Atomic Operations using Descriptor Tables #6717
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s on class instances using either pointer compress (disabled by default) or descriptor table indexes
|
Closing as it requires a rework and I do not currently have time to work on it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description seen at Issue #6663
Summary: Allows atomic operations using descriptor tables. Pointer compression is disabled by default (for now), mainly so that it can be tested. Unfortunately I cannot find a way to set compile-time flags for internal modules, as well I wasn't sure if everyone would agree on whether or not it deserved to be an internal module, so I placed it in 'modules/standard'. Willing to provide benchmark on request (although a few things have changed since then, such as refactoring for improved readability [hopefully...] and using tuples over chapel arrays for performance) but results may vary.