[pull] swiftwasm from main #4631
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Operator function witnesses are looked up globally. However, an additional, qualified lookup is warranted if the conforming type is declared in a local context.
Also, switch the build instructions in the doc to the much more common AArch64, add instructions to cross-compile a standalone stdlib with a prebuilt toolchain, and add missing Concurrency library and its dependencies to the list of Swift libraries to copy over.
…ent lib Fixes rdar://94184066.
Add regression tests to close several fixed issues
…lizers. Applying the `@_backDeploy` attribute to an initializer currently causes a duplicate symbol error at link time so for now reject it on those declarations for clarity. Also, reject it on deinitializers as well since the attribute cannot have the desired effect on `deinit`. Resolves rdar://94450734
…orrection [Concurrency] fix grammatically incorrect phrase in TaskGroup.swift
… library. Change the order of paths provided for `DYLD_LIBRARY_PATH` when running tests for the back-deployed concurrency library, so they supersede the ones in `/usr/lib/swift`. This way, we can test the back-deployed concurrency library even on OS's that have the concurrency library in them. It's not a complete test, because the standard library and runtime will still vary, but can reproduce many failures more easily. When using the back-deployed concurrency library, set the lit feature `back_deploy_concurrency`. Update some tests that are unsupported with back-deployment to check this. Finally, add some logging when the concurrency runtime cannot be tested at all, to help with debugging CI in the future.
…rency-rebuild Inline the Swift 5.6 concurrency library as a separate back-deploy library
…-on-init-deinit Sema: Diagnose `@_backDeploy` attributes on initializers and deinitializers
…loyment bots. Using XFAIL won't work here because the tests pass on the iOS back deployment bots, resulting in a UPASS. I was able to take a look at the test binary and rule out both codegen for `if #available(...)` and the optimizer as culprits so the next step is to check if `_stdlib_isOSVersionAtLeast()` is actually busted in the runtime libraries in older versions of macOS.
…ce-operator Sema: Fix operator function witness lookup for local adoptees
…rency-on-newer-os Make back-deployed concurrency library testable on OS's that have the library built-in
…unsupported-for-back-deployment Tests: Mark test/stdlib/StringCreate.swift as unsupported on back deployment bots
[android] Update to LTS NDK 23c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )