[pull] swiftwasm from master #1234
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}
…k to thin and thick to thick representations on subtype context
…rtain representation convertions do not crash
Co-authored-by: Xiaodi Wu <[email protected]>
…on map when computing necessary bindings of abstract cnditional requirements SR-12853
…of a global variable
When running build-script with --swift-inspect, the Package.resolved file is created in tools/swift-inspect. Ignore it.
to match the one specified in LLVM's Mach-O parser. Otherwise LLDB could not possibly find it! This name is used by the swift -modulewrap subcommand, which is currently unused on Darwin, and primarily intended for use under Linux. However, it may be useful to better support static archives (.a) files with Swift debug info in the future. To fully support this, dsymutil and LLDB need to know to look for Swift AST sections in Mach-O objects other than .dSYM bundled. Implementation note: It would be nice to get the section name out of libObject, but with the current architecture this needs a major refactoring that didn't seem justified, given that there is an end-to-end test to prevent such a mishap in the future. <rdar://problem/63991514>
Swift calls the architecture x86_64, OpenBSD calls it amd64. If we use run_cpu in lit.cfg as-is, then we may need to duplicate lines in each test for 'x86_64' and 'amd64', which puts a maintenance burden on unit test developers to ensure they are duplicating changes to each line. Instead, alias 'amd64' to 'x86_64' for `run_cpu`, but keep the platform module path referring to 'amd64', in order to distinguish the target architecture name and the Swift architecture name. This is particularly relevant for the %target-.*-name pseudovariables used, which should reference the Swift architecture names. However, some unit tests are directly referencing %target-cpu directly, which would break the aliasing. This is done only for swiftinterface files, so a new substitution is defined in lit.cfg for these variables, and the affected unit test cases are migrated.
but Solution node->type map is all or nothing, so can be cheaper.
The CI is switching to ICU 67 since there are fixes in the latter version of ICU that are needed. This should be further improved in the future to possibly use the the unicode.org releases.
This reverts commit 499ed05. This changes the num-threads passed to 1 to avoid a multithreaded output issue on windows
Allow user control over libxml2 usage via `LLVM_ENABLE_LIBXML2` rather than assuming that if it is found, it should be enabled.
[Sema] Solution nodeTypes from MapVector to DenseMap.
…epresentation conversions.
Update WindowsBuild.md
build: do not assume that XML2 should be enabled
…e-swift-inpect-products [Gardening] Ignored Package.resolved for swift-inspect.
Ignore onFastPath builtin while looking for valid static initializer of a global variable
…stractConditionalRequirements IRGen: Lookup the conformance of an archetype in the right substitution map when computing necessary bindings of abstract cnditional requirements
…-mappings-for-all-modules reland: Emit coverage mappings for all modules
…liasing [test] Handle architecture aliasing for OpenBSD.
Call prepareExtensions to make sure we load in any new extensions brought in by modules loaded after-the-fact. This isn't an issue for normal compilations as we load all the modules up-front in import resolution, but clients such as the LLDB REPL may load in modules later. Resolves rdar://64040436.
Fix the hardcoded Swift AST section / segment name for Mach-O
[SourceKit][SR-12837] Add effective access level of references
…entions [SR-12723][Sema] Validate function type param representations thick-to-thin conversions
Disable tests that occasionally flake on Linux. SR-13021 tracks re-enabling these tests.
MaxDesiatov
approved these changes
Jun 16, 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 : )