Skip to content

swift/tensorflow merge (2020-06-09) #1321

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

Merged
merged 42 commits into from
Jun 9, 2020
Merged

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Jun 9, 2020

No description provided.

fhahn and others added 30 commits June 2, 2020 19:08
…#1287)

Currently combineInsertEltToShuffle turns insert_vector_elt into a
vector_shuffle, even if the inserted element is a vector with a single
element. In this case, it should be unlikely that the additional shuffle
would be more efficient than a insert_vector_elt.

Additionally, this fixes a infinite cycle in DAGCombine, where
combineInsertEltToShuffle turns a insert_vector_elt into a shuffle,
which gets turned back into a insert_vector_elt/extract_vector_elt by
a custom AArch64 lowering (in visitVECTOR_SHUFFLE).

Such insert_vector_elt and extract_vector_elt combinations can be
lowered efficiently using mov on AArch64.

There are 2 test changes in arm64-neon-copy.ll: we now use one or two
mov instructions instead of a single zip1. The reason that we need a
second mov in ins1f2 is that we have to move the result to the result
register and is not really related to the DAGCombine fold I think.
But in any case, on most uarchs, mov should be cheaper than zip1. On a
Cortex-A75 for example, zip1 is twice as expensive as mov
(https://developer.arm.com/docs/101398/latest/arm-cortex-a75-software-optimization-guide-v20)

Reviewers: spatel, efriedma, dmgreen, RKSimon

Reviewed By: RKSimon

Differential Revision: https://reviews.llvm.org/D80710

(Cherry-picked from d20a3d3)
Extend TestSwiftDynamicSelf.py to inspect the children of self in Base &
Child inits.
Use raw string literals, reflow comments, exit early where possible, and
replace a bitwise-or with a logical-or operation.
This has no effect on the testsuite and was only needed in an early
prototype from before debugserver was able to report the correct
platform.

(cherry picked from commit 2d2a603)
This fixes an unhandled signed integer overflow in AddWithCarry() by
using the llvm::checkedAdd() function. Thats to Vedant Kumar for the
suggestion!

<rdar://problem/60926115>

Differential Revision: https://reviews.llvm.org/D80955

(cherry picked from commit a0b674f)
Fix UB in EmulateInstructionARM64.cpp
This patch adds support for Swift's UnsafeBufferPointer and
UnsafeMutableBufferPointer data formatting.

It introduces a summary provider and a synthetic frontend creator for
these types.

Signed-off-by: Med Ismail Bennani <[email protected]>
[gardening] Extend TestSwiftDynamicSelf.py, modernize WrapExpression
[lldb/formatter] Add Swift.UnsafeBufferPointer data formatter
Newer versions of clang reject this code.
[LLDB] nullptr and false are not the same
JDevlieghere and others added 12 commits June 5, 2020 10:22
Treat N_AST symbol table entries like other debug entries and don't emit
them in the linked binary.

Differential revision: https://reviews.llvm.org/D81205

(cherry picked from commit fe82d3a)
These functions really don't belong into PlatformDarwin, since they
actualy query state of the Host and not of the remote platform.

(cherry picked from commit 3d7b926)

 Conflicts:
	lldb/source/Plugins/Platform/MacOSX/PlatformDarwin.h
instead of preferring the one chosen with xcode-select.

<rdar://problem/64000666>

Differential Revision: https://reviews.llvm.org/D81210

(cherry picked from commit 79daa3d)
Teach GetXcodeSDK to look in the Xcode that contains LLDB
[dsymutil] Don't emit N_AST symbol entries in the Mach-O companion file
@compnerd
Copy link
Member Author

compnerd commented Jun 9, 2020

Tested with swiftlang/swift#32265

@compnerd compnerd merged commit ff7e5f2 into swift/tensorflow Jun 9, 2020
@compnerd compnerd deleted the swift/tensorflow-merge branch June 9, 2020 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants