-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8287281: adjust guarantee in Handshake::execute for the case of target thread being current #8992
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
Closed
Closed
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
14bee58
Disallow handshaking with self
jdksjolen b7b4c08
Call do_thread if handshaking with current thread as target
jdksjolen b40577f
Use is_handshake_safe_for and add the return
jdksjolen 8ddb442
Switch order of handshake check
jdksjolen e356932
Remove checks for is_handshake_for, instead call Handshake::execute
jdksjolen bf75d4c
do_thread(target) not self
jdksjolen d4aea87
Use current instead of self as name for current thread
jdksjolen c476d30
Remove unused variable
jdksjolen f2646e0
Move assert up and remove other assert, remove unused var
jdksjolen cc6736c
Check only for target == current
jdksjolen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
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.
I much prefer that the current-thread case is internalised by
Handshake::execute
now. The code creating the handshake op shouldn't have to worry about current thread or not.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.
Having
Handshake::execute()
handle the current-thread case will certainlyallow us to make the code consistent in all the callers of
Handshake::execute()
.