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

[mono][jit] Add some barriers to the delegate invoke code. #83673

Merged
merged 1 commit into from
Mar 21, 2023

Conversation

vargaz
Copy link
Contributor

@vargaz vargaz commented Mar 20, 2023

Re: #81123.

@lambdageek
Copy link
Member

runtime (Build Libraries Test Run release mono linux arm64 Debug) passed.

Going to trigger the pipeline a couple more times to be sure

@lambdageek
Copy link
Member

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lambdageek

This comment was marked as outdated.

@vargaz vargaz force-pushed the arm64-tramp-wbarrier branch from a1304f9 to cf30f80 Compare March 20, 2023 18:26
@lambdageek
Copy link
Member

arm64 passed Build Libraries Test Run release mono linux arm64 Debug. running again

@lambdageek
Copy link
Member

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vargaz vargaz changed the title [mono][jit] Add a read barrier to the arm64 delegate invoke trampoline. [mono][jit] Add some barriers to the delegate invoke code. Mar 20, 2023
@lambdageek
Copy link
Member

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lambdageek
Copy link
Member

With read and write barriers, linux-arm64 passed twice. I guess if it passes one more time we should merge it and see if the overall reports in #81123 go down. Thanks for tracking it down @vargaz

@lambdageek
Copy link
Member

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vargaz vargaz marked this pull request as ready for review March 21, 2023 18:03
@ghost ghost locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants