-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Merge tag 'swift-DEVELOPMENT-SNAPSHOT-2019-10-31-a' into tensorflow #28080
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
Conversation
[SyntaxParse] Remove unnecessary verifyElementRanges() call
[ClangImporter] Fix edge cases where custom name matches native name
This adjusts the encoded RPATH to enable us to switch to the new Foundation build.
[build-script] Add preset to set up CI testing for the stress tester
[CS] Make resolveLocatorToDecl simpler and more robust
Also fix a comment typo while I'm here.
...not the one they came from. This is important when specializing an inlinable function that takes an opaque type as a generic argument: that opaque type should still be considered opaque even if it came from the same module as the inlinable function. rdar://problem/56410009
No functionality change.
build: adjust rpath for new foundation layout
…warning-unecessary-casts
getInterfaceType() will return an ErrorType if the declaration is currently being validated, which can happen if override checking triggers associated type inference. I believe this is <rdar://problem/47220065>.
…med superclass type It is possible for getSuperclassDecl() to return a non-null type, while getSuperclass() returns an ErrorType. In this case, getContextSubstitutions() could crash because the walk of the superclass chain via getSuperclass() might not find the context class. Instead of crashing in asserts builds, let getContextSubstitutions() silently build an invalid substitution map here, just as it does in no-asserts builds.
Remove clone commands for curl and libxml2 as they are prebuilt now.
A couple of small circularity fixes
Update WindowsBuild.md
[windows] Add folder to path while testing.
[build-script] Don't build stdlib for iOS if --skip-build-ios is passed
[CMake] Fix the static bindings workflow.
…warning-unecessary-casts
…toneye-joe OpaqueArchetypeSpecializer: inlinable functions are now in this module
…ration for that being a semantic accessor.
Diagnose the fact that we're missing a colon, not the fact that we're missing a type since that's actually what has gone wrong.
[cmake] Install runtime swiftDemangle pieces.
rdar://problem/53400364
Fix `KeyPathIterable` derived conformances: `KeyPathIterable.allKeyPaths` synthesis logic now uses different key-path expression coercion logic to accommodate upstream type-checker changes. See TF-575 for more information.
* Disable expected SILOptimizer test failures. These tests fail because `-enable-ownership-stripping-after-serialization` has been disabled for libswiftCore on tensorflow branch due to SR-11336. TF-799 tracks re-enabling these tests. * Fix libInMemoryFrontend unittests. * Remove test/IRGen/copy_value_destroy_value.sil. The test was deleted upstream in #27866.
@swift-ci Please clean test tensorflow |
I just launched a toolchain build for this branch. Let's see what happens with that. Otherwise, looks good! |
Full log for building LLDB here.
I won't investigate these LLDB issues further, but I will report results for macOS:
|
Upstream recently added `registerIDERequestFunctions`. We had previously added it as a tensorflow patch. So we're now calling it twice, which is forbidden. This PR removes our call, putting us in sync with upstream. This fixes the following error from swiftlang/swift#28080 (comment): ``` lldb: /home/danielzheng/swift-merge2/swift/lib/AST/Evaluator.cpp:58: void swift::Evaluator::registerRequestFunctions(swift::Zone, ArrayRef<swift::AbstractRequestFunction *>): Assertion `zone.first != zoneID' failed. ```
Related upstream patches: - #27871 - swiftlang/swift-syntax#160
Downstream repo tests reveal some additional errors that I'll investigate. swift-apis:
swift-quotes:
|
@swift-ci please test tensorflow |
1 similar comment
@swift-ci please test tensorflow |
@swift-ci please clean test tensorflow |
Introduced in swiftlang#28080: `swift-DEVELOPMENT-SNAPSHOT-2019-10-31-a -> tensorflow` merge.
Introduced in #28080: `swift-DEVELOPMENT-SNAPSHOT-2019-10-31-a -> tensorflow` merge.
No description provided.