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

Ensure we do not corrupt RAX for CFG dispatcher on x64 #70016

Merged
merged 1 commit into from
Jun 1, 2022

Conversation

jakobbotsch
Copy link
Member

The jump stubs used on x64 will clutter rax which is used for the target
address in the CFG dispatcher. When this happened for the CFG dispatcher
it would result in an infinite loop.

The same problem is already handled for some other helpers as pointed
out by @jkotas, so simply add the CFG dispatcher to that set.

The jump stubs used on x64 will clutter rax which is used for the target
address in the CFG dispatcher. When this happened for the CFG dispatcher
it would result in an infinite loop.

The same problem is already handled for some other helpers as pointed
out by @jkotas, so simply add the CFG dispatcher to that set.
@jakobbotsch
Copy link
Member Author

/azp run jit-cfg

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jakobbotsch
Copy link
Member Author

Failures are only in the CFG+gcstress jobs and look like #69657, #69662 and #69976.

@jakobbotsch jakobbotsch merged commit f7a32c0 into dotnet:main Jun 1, 2022
@jakobbotsch jakobbotsch deleted the cfg-dispatcher-via-indir branch June 1, 2022 09:42
@ghost ghost locked as resolved and limited conversation to collaborators Jul 1, 2022
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