Skip to content

Fix a debug info regression introduced with async support. #37844

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

Merged
merged 1 commit into from
Jun 10, 2021

Conversation

adrian-prantl
Copy link
Contributor

@adrian-prantl adrian-prantl commented Jun 9, 2021

This patch removes a heuristic to promote all debug intrinsics pointing into
allocas to llvm.dbg.declare() intrinsics and instead more accurate classifies
variables in async contexts by adding the missing cases alloc_box and
alloc_stack cases.

rdar://78977132

  • Explanation: Fix a debug info regression that causes an LLVM assertion failure and incorrect debug info in optimized code.
  • Scope: Debug info / optimized code
  • Risk: change only affects debug info
  • Issue: rdar://78977132

@adrian-prantl adrian-prantl requested a review from a team as a code owner June 9, 2021 03:20
@adrian-prantl
Copy link
Contributor Author

@swift-ci test

@adrian-prantl adrian-prantl requested review from fredriss and vedantk June 9, 2021 15:44
@adrian-prantl
Copy link
Contributor Author

@swift-ci nominate

@adrian-prantl
Copy link
Contributor Author

This was actually caught by the modified inlined-generics testcase, but I didn't pay enough attention to that at the time, not realizing what problem this would cause in the backend.

This patch removes a heuristic to promote all debug intrinsics pointing into
allocas to llvm.dbg.declare() intrinsics and instead more accurate classifies
variables in async contexts by adding the missing cases alloc_box and
alloc_stack cases.

rdar://78977132
@adrian-prantl
Copy link
Contributor Author

@swift-ci test

@adrian-prantl adrian-prantl merged commit d13c81d into swiftlang:release/5.5 Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants