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

Disable loading scalars as addresses when materializing an entity variable (swift/release/5.3) #1454

Conversation

augusto2112
Copy link

@augusto2112 augusto2112 changed the title Disable loading scalars as addresses when materializing an entity variable Disable loading scalars as addresses when materializing an entity variable (swift/release/5.3) Jul 14, 2020
@adrian-prantl
Copy link
Member

@fredriss (our release manager)
Given how easy it is to trigger this, I recommend cherry-picking this patch to 5.3. It fixes a bug when using generic values in the expression evaluator if they are stored in a register. The fix works by reverting an old workaround and restores the code to the form it has on llvm.org.

(The test is going to be updated shortly, so ignore that for now)

@adrian-prantl
Copy link
Member

@augusto2112 When cherry-picking a commit, pease use git cherry-pick -x, it adds a line to the commit message that makes it obvious that this is a cherry-pick.

@augusto2112
Copy link
Author

@adrian-prantl Ok! I'll do it next time!

@adrian-prantl
Copy link
Member

@augusto2112 can you update the test here?
Also, I just realized: was the test missing from the master-next PR? Could you make a newPR for adding the test to master-next?

@augusto2112
Copy link
Author

@adrian-prantl you're right, I forgot to update it there too. I'll create a new PR.

@augusto2112 augusto2112 force-pushed the class-constrained-protocol-eval-5.3 branch from 33c2811 to 5ca75b9 Compare July 15, 2020 17:12
@augusto2112
Copy link
Author

@adrian-prantl test updated!

@adrian-prantl
Copy link
Member

@swift-ci test

@fredriss fredriss merged commit 13a8e5d into apple:swift/release/5.3 Jul 16, 2020
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.

None yet

3 participants