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

JIT: Handle GT_SWIFT_ERROR_RET in LinearScan::getKillSetForNode #102519

Merged
merged 1 commit into from
May 22, 2024

Conversation

amanasifkhalid
Copy link
Member

Fixes #102349. In LinearScan::getKillSetForNode, GT_SWIFT_ERROR_RET (which represents the regular return value, alongside the Swift error register value to be loaded) needs to be handled like GT_RETURN if Compiler::compIsProfilerHookNeeded is true, which is possible under some JitStress scenarios.

This failure was found by runtime-coreclr jitstress-random setting DOTNET_JitStress=da -- I'm not sure how (or if) I can force CI to use the same env to verify correctness...

cc @dotnet/jit-contrib

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label May 21, 2024
@amanasifkhalid
Copy link
Member Author

/azp run runtime-coreclr jitstress-random

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

@amanasifkhalid
Copy link
Member Author

@EgorBo PTAL, thank you! The jitstress-random failures on x86 are unrelated (Swift tests run only on osx x64 and arm64), and the libraries test failure is #100616. Build Analysis is blocked by a bunch of timeouts on Linux x64...

Copy link
Member

@EgorBo EgorBo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing it

@amanasifkhalid
Copy link
Member Author

/ba-g Linux x64 timeouts are blocking clean CI

@amanasifkhalid amanasifkhalid merged commit 301604e into dotnet:main May 22, 2024
114 of 125 checks passed
@amanasifkhalid amanasifkhalid deleted the swift-error-ret-fix branch May 22, 2024 14:06
steveharter pushed a commit to steveharter/runtime that referenced this pull request May 28, 2024
…2519)

Fixes dotnet#102349. In LinearScan::getKillSetForNode, GT_SWIFT_ERROR_RET (which represents the regular return value, alongside the Swift error register value to be loaded) needs to be handled like GT_RETURN if Compiler::compIsProfilerHookNeeded is true, which is possible under some JitStress scenarios.
Ruihan-Yin pushed a commit to Ruihan-Yin/runtime that referenced this pull request May 30, 2024
…2519)

Fixes dotnet#102349. In LinearScan::getKillSetForNode, GT_SWIFT_ERROR_RET (which represents the regular return value, alongside the Swift error register value to be loaded) needs to be handled like GT_RETURN if Compiler::compIsProfilerHookNeeded is true, which is possible under some JitStress scenarios.
@github-actions github-actions bot locked and limited conversation to collaborators Jun 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SwiftErrorHandling: Assertion failed 'killMask == getKillSetForNode(tree)'
2 participants