Skip to content

[pull] swiftwasm from main #1884

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 28 commits into from
Oct 2, 2020
Merged

[pull] swiftwasm from main #1884

merged 28 commits into from
Oct 2, 2020

Conversation

pull[bot]
Copy link

@pull pull bot commented Oct 2, 2020

See Commits and Changes for more details.


Created by pull[bot]. Want to support this open source service? Please star it : )

hborla and others added 28 commits September 26, 2020 18:58
…nside an

initializer, and for wrapped local variables.
checks to check for type context instead of local context.

This generalization will help us implement property wrappers on
global variables, which should use the same approach of not adding
synthesized accessors to the AST and instead lazily visit them in
SILGen.
captured local variables for the assign_by_wrapper setter.

Since assign_by_wrapper will always be re-written to initialization
if the captured local variable is uninitialized, it's unnecessary
to mark the capture as an escape. This lets us support out-of-line
initialization for local property wrappers.
See also swiftlang#33383 where this problem is better explained.

MSVC doesn't seem to trigger the exception code when no frame pointers are generated. The only thing missing would be for interpreted code to have a more informative crash message.

Add a new LLVM Lit feature with the value of the VisualStudioVersion environment variable (it seems to not change even for minor versions, so it is an easy way to figure out the 2017/2019 difference, even if updates are applied).

Use the new feature in a XFAIL check in the test.
…ceLoader

This refactoring allows us to drop ModuleInterfaceLoader when explicit modules
are enabled. Before this change, the dependencies scanner needs the loader to be
present to access functionalities like collecting prebuilt module candidates.
…ngle-expression function

This information could be inferred from state recorded in a
constraint system, so to need to record that in the
constraint locator as well.
…-of-big

Sema: Move preCheckExpression() into its own file
…e-element

[ConstraintSystem] Infer whether locator is related to return of a si…
just like we do for regular non-member properties.
SILCombine maintains a worklist of instructions and deleting of instructions is valid only via callbacks that remove them from the worklist as well. It calls swift::tryDeleteDeadClosure which in turn calls SILBuilder apis like emitStrongRelease/emitReleaseValue/emitDestroyValue which can delete instructions via SILInstruction::eraseFromParent leaving behind a stale entry in SILCombine's worklist causing a crash.

This PR adds swift::emitDestroyOperation which correctly calls the appropriate InstModCallbacks on added/removed instructions. This comes from swift::releasePartialApplyCapturedArg which was handling creation of destroys with callbacks correctly.
[NFC] Add an iterator template for walking singly-linked lists
[Property Wrappers] Support local property wrappers
* Update docs/README.md
* Update docs/contents.rst
…-2017-test

[windows] XFAIL crash-in-user-code test in MSVC 2017
…rface-loader

ModuleInterface: refactor ModuleInterfaceChecker out of ModuleInterfaceLoader
@pull pull bot merged commit ecd0d8e into swiftwasm Oct 2, 2020
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.