[pull] swiftwasm from master #673
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}
Currently, tests are scattered throughout multiple directories, making it difficult to determine what is tested and what is not tested. With upcoming work on interoperability between Swift and C++ (https://forums.swift.org/t/manifesto-interoperability-between-swift-and-c/33874), we'd like to rearrange the tests and bring tests covering a single C/C++ feature next to each other. This PR also adds tests for enabling C++ interop where possible.
This code directly references several sections in the __TEXT segment but the comment refers to __DATA.
innermost call to init(wrappedValue:) if the target is for initialization of a property wrapper's backing storage.
wrapper original wrapped value expression inside of CSApply. This prevents type checking the synthesized backing storage initializer twice - once with the original expression and again with the placeholder.
…s that involve inout closure parameters and were previously type checked twice.
initializer for property wrappers that are not memberwise initialized but have an explicit original wrapped value.
wrapped value placeholder in an init(wrappedValue:) call that was previously injected as an OpaqueValueExpr. This commit also restores the old design of OpaqueValueExpr.
… example of how to use llvm's bisect tool to autobisect the optimizer.
…ng a property wrapper backing init if the property type doesn't match the wrapped value type.
Support the usual `--enable-*san options`, but also add a `--test-indexstore-db-santitize-all` that runs the tests once for each sanitizer. Sanitizing just indexstore-db with a regular toolchain should be much faster than using sanitized compilers.
Explicitly pass the path to the python interpreter on macOS by using `xcrun` to find the tools.
rdar://problem/61734317
New versions of Python warn if the literal is not escaped. Specifically:
"Support for nested sets and set operations in regular expressions as in
Unicode Technical Standard #18 might be added in the future. This would
change the syntax. To facilitate this future change a FutureWarning will
be raised in ambiguous cases for the time being. That include sets
starting with a literal '[' or containing literal character sequences
'--', '&&', '~~', and '||'. To avoid a warning, escape them with a
backslash. (Contributed by Serhiy Storchaka in bpo-30349.)"
https://docs.python.org/dev/whatsnew/3.7.html
build: explicitly pass the path to python2,python3
…8480-indirect-default-impls [SymbolGraph] Look at inherited protocols for default implementations
Split `emitDiagnostic` into `emitDiagnostic` and `emitDiagnosticAt`. Refactor existing diagnostics to use new methods and avoid passing location when possible.
Python3 sometimes doesn't get found, add a temporary workaround.
test: Add parens to print for Python3 compatibility
…6c645418a458613034c1d6c
… tests to ContinuousIntegration.md.
…2b76de571e9903b70c2adf1 [docs] Add a section on running @swift-ci based non-executable device tests to ContinuousIntegration.md.
…n-implicit-rdar61075677 [SourceKit] Don't use clang build sessions when validation is disabled
…53c227ec20517db745d6131 [doc] Describe how to use git-bisect in the presence of branch forwarding/feature branches.
build: add a workaround for the build to use Python2 instead of Python3
[benchmark] Package.swift: Don’t trap on stray files under single-source/
…UninitializedCapacity:initializingWith:)` (swiftlang#30133) * Removes redandant buffer zeroing * Fixes typo * Fix compile error
[AutoDiff] Add `REQUIRES: CPU=x86_64` to IRGen test.
runtime: extend shims to x86
…wiftlang#30979) * Don't crash when missing a type in a Diagnostic message. Print an empty string for the missing type. Resolves SR-12460 * Added new diagnostic message, eg. "operator '==' declared in extension must be 'static'"
…leanup clean up some stdlib unittest warnings
…pi-digester-dsym Disable creating swift-api-digester dSYM to reduce toolchain size
…nostic [Diagnostics] Introduce `getLoc` and `getSourceRange` to failure diagnostic
…mbols toolchain size
Fixed incorrect comment in SwiftReflectionTest
…r-from-swift! Runtime: Implement wrapper function to call metadata access functions
[benchmark] Add HTTP2StateMachine benchmark
…nfo-only [Preset] Generate line number debug information only to reduce the sy…
MaxDesiatov
approved these changes
Apr 15, 2020
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]. Want to support this open source service? Please star it : )