Skip to content

[pull] swiftwasm from main #3729

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 20 commits into from
Oct 17, 2021
Merged

[pull] swiftwasm from main #3729

merged 20 commits into from
Oct 17, 2021

Conversation

pull[bot]
Copy link

@pull pull bot commented Oct 16, 2021

See Commits and Changes for more details.


Created by pull[bot]

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

finagolfin and others added 19 commits October 12, 2021 12:37
The latest Long Term Support NDK finally removed binutils, including the bfd/gold
linkers and libgcc. This simplifies our Android support, including making lld the
default linker for Android. Disable three reflection tests that now fail, likely
related to issues with swift-reflection-dump and switching to lld.

Also, add the libatomic dependency for Android armv7, just as on linux.
Replaced a SmallSetVector worklist with a GraphNodeWorklist to avoid
infinitely pushing and popping the same value the same value into and
out from the worklist.
Required before fixing/re-enabling OSSA RAUW utilities.

Make sure the SILCombine worklist canonicalizes all the copies and
guarantees termination.

Run canonicalization on every existing copy_value once
and once for every new copy_value added during SILCombine.

Only add copies and their uses back to the worklist if
canonicalization deleted an instruction.

Add tracing for sinking forwaring instructions.
Seems to be a difference between debug and release. var vs let is
harmless here, but we should still investigate what's causing the
difference.

The change introducing the failure should be somewhere between
36b9c79 and
6e07ee8.

For now remove the match to get CI passing again.
Marker protocols don't exist at runtime, drop them when mangling a type
for the purposes of runtime type metadata or reflection. Fixes
rdar://82314404.
Previously, all phi arguments added to the backedge block were given
@owned ownership.  That was not correct for arguments that needed to
have @guaranteed ownership.  Here, that is corrected by using the
ownership of the original argument from the header block when adding the
phi argument to the backedge block.
SILCombine - Fix worklist logic for OSSA canonicalization
…dagnodeworklist-in-visittransitiveendborrows

Used DAGNodeWorklist in visitTransitiveEndBorrows.
…tors.

Fix a few minor issues in the type checker and SILGen to properly cope with
distributed functions defined within extensions of distributed actors.
While here, centralize the logic that adds the "_remote_" function.

Fixes rdar://84325525.
Distributed thunks were using the same mangling as direct method
reference thunks (i.e., for "super" calls). Although not technically
conflicting so long as actors never gain inheritance, it's confusing
and could cause problems in the future. So, introduce a distinct
mangling for distributed thunks and plumb them through the demangling
and remangler.
[Test] Remove failing match in SILGen/newtype.swift
…kedge-ownership

[LoopRotate] Use ownership for backedge block.
…k-23

Revert "[android] Update to NDK 23"
@pull pull bot added the merge-conflict Resolve conflicts manually label Oct 16, 2021
@MaxDesiatov MaxDesiatov enabled auto-merge October 16, 2021 21:49
@MaxDesiatov MaxDesiatov merged commit 001dd21 into swiftwasm Oct 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants