Skip to content

[pull] swiftwasm from main #2658

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 39 commits into from
Feb 5, 2021
Merged

[pull] swiftwasm from main #2658

merged 39 commits into from
Feb 5, 2021

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 4, 2021

See Commits and Changes for more details.


Created by pull[bot]

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

meg-gupta and others added 30 commits February 2, 2021 14:01
The noasserts flavor was previously XFAILed.

rdar://72856256
The insert point may not have RegularKind debug location.
So, use an auto-generated RegularKind debug location.
We were adjusting the lifetime of the final phi created by the
SSAUpdater. The intermediate phi's lifetime needs to be adjusted as
well.
This visits unique pairs of reborrowPhi and its base value.
The code for the utility is mostly refactored from the ReborrowVerifier.

This utility will be used later in DCE.
A reborrow's base value may change if the base value is also passed as
an operand on a branch. Record reborrow dependencies so that we can mark
the base value as live, if the reborrow was also live. This ensures we
do not insert destroy_value on the base value prematurely before the
lifetime of the reborrow ends.
Nested borrow handling can be complex in the presence of reborrows. So
it is not handled currently.
…odes

Remove this distinction without a difference. Originally, the thought
was to
1) Isolate the cross-module build infrastructure
2) Provide a signal to the driver that a dependency had swiftdeps info
   in it

But the driver need only notice swiftmodule files as external
dependencies and try to extract that information if it can to divine the
signal it needs. Additionally, we can give it fingerprints as priors to
let it know there might be incremental info to be had.
for applied overloads when selecting a disjunction to attempt.
…ve COWBufferReading builtin in the FileCheck test.
Usually debug info only ever describes the *result* of a projectBox
call. To display a boxed parameter of an async continuation object,
however, the debug info can only describe the box itself and thus also
needs to emit a box type for it so the debugger knows to call into
Remote Mirrors to unbox the value.

SR-14059
rdar://problem/73358988
We've seen bad file descriptor errors in certain build environments (rdar://73157185) and retrying
opening those files seems to be a walkaround. In this change, we allow the
compiler to retry expanding reponse files in argument lists.

rdar://73892564
…odules

`InterfaceSubContextDelegateImpl` causes sub-instances to inherit `-fmodule-map-file=` options.
Those Module Maps become file dependencies of all downstream PCMs and their depending Swift modules, even though they really aren't.
This causes frequent re-builds of the Module Cache contents when seemingly-unrelated files are touched.

Explicit Module Builds rely on these options for building Swift Interface files, so for now we just disable inheritance of these options in Implicit Module builds.
Foundation imports `free`, importing it as `dllimport dso_local` which
is not permitted.  Clean up the IRGen to ensure that the two are not
emitted together.
Frontend: allow retrying expanding response files in argument lists
Support SILBoxWithLayout in TypeDecoder
Add debug info support for boxed arguments in async functions.
…rgsInSubContexts

Avoid false FileDependnecies among Implicitly-build Swift and Clang modules
hborla and others added 7 commits February 4, 2021 09:01
…ection

[ConstraintSystem] Tweak disjunction selection
This should reduce the frequency of module errors due to shared module caches between runs on the same Linux bot.

The list of presets affected should be

```
buildbot_incremental_linux
buildbot_incremental_linux,asan
buildbot_incremental_linux,llvm-only
buildbot_incremental_linux,long_test
buildbot_incremental_linux,tsan-libdispatch-test
buildbot_incremental_linux_1404
buildbot_incremental_linux_1404,long_test
buildbot_incremental_linux_base
buildbot_linux
buildbot_linux,foundation=debug
buildbot_linux,foundation=release
buildbot_linux,no_test
buildbot_linux,smoketest
buildbot_linux_1404_no_lldb
buildbot_linux_1510
buildbot_linux_1510,notest
buildbot_linux_1604
buildbot_linux_1604,notest
buildbot_linux_1610
buildbot_linux_1610,notest
buildbot_linux_1804
buildbot_linux_1804,notest
mixin_linux_installation
```

Addresses rdar://73932610, rdar://73933230
Fix lifetime of intermediate phis created by the SSAUpdater for RLE
…Methods

SE-0267 makes this legal in Swift, but these constraints are
unrepresentable in Objective-C and often lead to blow-ups in SILGen when
we construct invalid SIL signatures.

rdar://71845752
…en/rdar72357371-3

[IRGen] Sign task resume context in swift_suspend_point.
…-generically

Ban @objc Methods that Introduce Constraints on Contextually Generic Methods
meg-gupta and others added 2 commits February 4, 2021 15:16
…763f05388b53f577ef9a5e4

[sil-combine] Fix a test to be i386 independent and make sure we remove COWBufferReading builtin in the FileCheck test.
@kateinoigakukun kateinoigakukun merged commit 9f1cc50 into swiftwasm Feb 5, 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.