Skip to content

LICM: fix a wrong tuple type when splitting loads #82012

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 5, 2025

Conversation

eeckstein
Copy link
Contributor

  • Explanation: This fixes a compiler crash cause by loop invariant code motion (LICM). When splitting load instructions, LICM created a tuple instruction without specifying the type. This caused a SIL type mismatch error in case original tuple type of the load has labels.
  • Risk: Low. It's a very trivial change which only affects the SIL type of an instruction.
  • Testing: Tested by a lit test.
  • Issue: rdar://152588539
  • Reviewer: @atrick
  • Main branch PR: LICM: fix a wrong tuple type when splitting loads #81987

When creating a tuple, the type needs to be specified because otherwise, if the original tuple has labels, it will cause a type mismatch verification error.

rdar://152588539
@eeckstein eeckstein requested a review from a team as a code owner June 5, 2025 05:26
@eeckstein
Copy link
Contributor Author

@swift-ci test

@eeckstein eeckstein merged commit 121aa40 into swiftlang:release/6.2 Jun 5, 2025
5 checks passed
@eeckstein eeckstein deleted the fix-licm-6.2 branch June 5, 2025 15:28
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.

2 participants