Skip to content

[pull] swiftwasm-release/5.4 from release/5.4 #2743

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 6 commits into from
Feb 16, 2021
Merged

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 15, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

eeckstein and others added 5 commits February 12, 2021 15:20
…nal<reference> as an operand

strong_retain/strong_release with an optional reference as operand are rejected by the verifier and are not supported by IRGen.
SILCombine created such retains/releases when optimizing ref_cast instructions.

This fixes a compiler crash.
rdar://74146617
…ceWritableKeyPaths.

Call through to _swift_modifyAtReferenceWritableKeyPath_impl in that case. This fixes an assertion failure (or worse) when upcasting a ReferenceWritableKeyPath and then using subscript(keyPath:) to modify a value with it.

rdar://74191390
(cherry picked from commit a84a3a8)
…peAliasDecl with a dependent underlying type

Fixes https://bugs.swift.org/browse/SR-11639 / rdar://problem/56466696
…st-5.4

[5.4] SILCombine: don't create a strong_retain/strong_release with an Optional<reference> as an operand
…olved-dmt-fix-5.4

GSB: An unresolved DependentMemberType might resolve to a concrete TypeAliasDecl with a dependent underlying type [5.4]
…eyPath-5.4

[5.4][Stdlib] Fix _swift_modifyAtWritableKeyPath_impl to check for ReferenceWritableKeyPaths.
@pull pull bot merged commit 9d3b2e5 into swiftwasm-release/5.4 Feb 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants