[pull] swiftwasm from master #13
Closed
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}
…orts Fix dependency scanner test-case to use explicit imports
…modules To support -disable-implicit-swift-modules, the explicitly built modules are passed down as compiler arguments. We need this new module loader to handle these modules. This patch also stops ModuleInterfaceLoader from building module from interface when -disable-implicit-swift-modules is set.
…ite to memory. This is an older verifier that checks that uses of addresses from things like in_guaranteed parameters are never written to. We just never hit this before. <rdar://problem/63188699>
…1d79077537f42c392666592 [semantic-arc-opts] Create an explicit composition type for "ownership phi operands".
…h multiple non-trivial values. Just like br inst, structs are phis in the ownership graph that one can induce on top of the def-use graph. In this commit, I basically fill in the relevant blanks in the ADT for such phis for struct so that the optimization for branches is generalized onto structs. <rdar://problem/63950481>
Front-end: add a new module loader that loads explicitly built Swift modules
…ession Rather than using various "applied function builder" and "is single expression body" checks to determine whether a closure was type-checked in its enclosing expression, record in the closure expression whether it actually *was* type-checked as part of its enclosing expression.
…osing expr Introduce a new predicate, shouldTypeCheckInEnclosingExpression(), to determine when the body of a closure should be checked as part of the enclosing expression rather than separately, and use it in the various places where "hasSingleExpressionBody()" was used for that purpose.
…for-dynamic-member-lookup-indexing-crasher [test] Add indexing regression test case for @dynamicMemberLookup on a protocol.
…ndex-ignore-system-modules-to-clang-modules [Index] Apply -index-ignore-system-modules to system clang modules
As of c90e198, clang is now more strict about parsing of enum-base in order to follow C++11 rules.
… getenv when possible. There are a few environment variables used to enable debugging options in the runtime, and we'll likely add more over time. These are implemented with scattered getenv() calls at the point of use. This is inefficient, as most/all OSes have to do a linear scan of the environment for each call. It's also not discoverable, since the only way to find these variables is to inspect the source. This commit places all of these variables in a central location. stdlib/public/runtime/EnvironmentVariables.def defines all of the debug variables including their name, type, default value, and a help string. On OSes which make an `environ` array available, the entire array is scanned in a single pass the first time any debug variable is requested. By quickly rejecting variables that do not start with `SWIFT_`, we optimize for the common case where no debug variables are set. We also have a fallback to repeated `getenv()` calls when a full scan is not possible. Setting `SWIFT_HELP=YES` will print out all available debug variables along with a brief description of what they do.
The host platform should be using `CMAKE_SYSTEM_NAME STREQUAL Darwin`. However, we currently drive the host side of the compilation against custom variables. This makes the migration simpler by ensuring that the entire file uses the same pattern. Since `is_darwin_based_sdk` is now used only in the standard library build, sink it to the standard library build.
`classMetadata` is only used in the ObjC path, resulting in a `-Wunused-variable` warning. Sink the variable into the ObjC path. Because the conversion of the metadata does not rely on the type metadata bits in the metadata, it is safe to delay the definition and bit adjustment to the point where it is used unifying the two ObjC paths.
…resLinkPthread [stdlib][cmake] OpenBSD target requires -lpthread.
SIL: Verify kinds of vtable entries.
…wiftlang#32133) * Add note that LLDB changes should be cherry-picked to `swift/master` * New Swift-dependent commits should go to `swift/master`, not `swift/master-next`. * Update naming scheme for release branches * Fix indentation
…wiftlang#32181) This reverts commit f7473a7.
…closure-cleanup [AST] Clean up handling of single-expression closures
…8390-inherit-availability [SymbolGraph] Inherit availability from parent contexts
ABI: qualify use of `StringRef` and `Optional` (NFC)
[NFC] AST: Optimize GenericSignatureImpl::getInnermostGenericParams
…03c93f1ba6ac111c52d1157 [semantic-arc-opts] Teach semantic-arc-opts how to handle structs with multiple non-trivial values.
[CSGen] Allow `is` patterns to infer type from enclosing context
Add a new `PrintInherited` flag to `PrintOptions` to support this. rdar://63033669
runtime: silence -Wunused-variable warning (NFC)
…c54f4b3c46468e4706e7c80 [memory-lifetime] Teach the verifier that select_enum_addr doesn't write to memory.
…als_arm64 Fix c_globals.swift test on arm64
These tests are marked XFAIL or UNSUPPORTED because either the tests: require libc annotation, require Mach-O support, don't recognize calls to swift-autolink-extract, requires porting alongside Linux, or rely on simd which is not present. Additionally, explicit REQUIRES for tsan/asan/fuzzer are added to some tests, since OpenBSD does not support these sanitizers or fuzzers, since it's nicer to mark that with REQUIRES rather than XFAIL.
…965160 [CodeCompletion] Wrap base expression with CodeCompletionExpr
…ed-convenience-inits-for-members [ClangImporter] Make sure that inherited convenience constructors are included in members of `IterableDeclContext`
…sourcekit-driver-args [Driver/SourceKit] Handle filelist driver args in getSingleFrontendInvocationFromDriverArguments
…tion Strip TypeLoc out of Patterns
Inline it into its final user: swift::performTypeLocChecking
…366ae4af217d8279439f36e
…e-modules Revert "Emit coverage mappings for all modules"
Strip Attributes of their TypeLocs
…AndRequired [test] Mark XFAIL tests for OpenBSD.
…format New binary swiftdeps format
…dead-param [NFC] CS: Inline a parameter in openUnboundGenericType
…e_metadata_in_conditional_reqts IRGen: Note use of types in conditional requirements of protocol conformances
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 : )