Skip to content

Merge tensorflow-merge into tensorflow #27751

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 4,218 commits into from
Oct 17, 2019
Merged

Merge tensorflow-merge into tensorflow #27751

merged 4,218 commits into from
Oct 17, 2019

Conversation

asuhan
Copy link
Contributor

@asuhan asuhan commented Oct 17, 2019

No description provided.

swift-ci and others added 30 commits September 28, 2019 03:23
discovering the beginning of the string interpolation passed
to os log APIs.

The implementation follows the chain of dependencies starting
from an initializer call to OSLogMessage until the first
instruction of interpolation is discovered. This is more
robust towards changes to the SIL generation of string
interpolation literals.
This allows us to define a `LocatorPathElt`
subclass for each path element kind.
This makes it consistent with `getLastElementAs`
and `castLastElementTo`.
Rename to LocatorPathElt::ProtocolRequirement in
order to help avoid confusion with
LocatorPathElt::AnyRequirement.
…e type yet

Fixes rdar://55560962 and https://bugs.swift.org/browse/SR-11495

This bug was caused because we'd fail to lookup C in B, because we
hadn't computed its type yet and therefore B is filtered from lookup.
Just remove the filter for interface type.
Recently introduced tests have some of their path separators output with
Windows separators. Adapt the test to account for the different output
in Windows.
Structurally prevent a number of common anti-patterns involving generic
signatures by separating the interface into GenericSignature and the
implementation into GenericSignatureBase.  In particular, this allows
the comparison operators to be deleted which forces callers to
canonicalize the signature or ask to compare pointers explicitly.
[CS] Define a class for every locator path element kind
[NFC] Adopt TypeBase-isms for GenericSignature
…nches for testing purposes

I am going to use this in a subsequent commit to make sure we do not infinite
loop upon a test case.

rdar://55861081
… prevent infinite loops.

Previously, we were not handling properly blocks that we could visit multiple
times. In this commit, I added a SmallPtrSet to ensure that we handle all of the
same cases that we handled previously.

The key reason that we want to follow this approach rather than something else
is that the previous algorithm on purpose allowed for side-entrances from other
checks since often times when we have multiple checks, all of the .none branches
funnel together into a single ultimate block.

This can be seen by the need of this code to support the test two_chained_calls
in simplify_switch_enum_objc.sil.

rdar://55861081
[windows][test] Use regexes for some (more) path separators.
…#27412)

Two places in Driver are creating temporary files at a point in the
process where failure is not expected. We should do something better
about this, but meanwhile harmonize their failures and include a
little more info.

Filed https://bugs.swift.org/browse/SR-11541 to improve this.
Identifier contains a pointer to character data, and we need to ensure that this pointer has enough spare bits in it for DeclBaseName and DeclName. This currently happens to be true because the StringMap used to intern Identifier pointers happens to place a 32-bit size field in the MapTableEntry object, but it would be better to explicitly force the alignment we want and assert that it’s correct.
…ing-superclass

[Deserialization] Allow lookup into decls that don't have an interface type yet
…block

Disabled checking in blocks which end up in an unreachable-instruction.
Inconsistent states are allowed in such blocks.

https://bugs.swift.org/browse/SR-11545
rdar://problem/55842518
@asuhan asuhan requested review from rxwei and dan-zheng October 17, 2019 05:24
@asuhan
Copy link
Contributor Author

asuhan commented Oct 17, 2019

Had a few minor conflicts following today's cleanups in the tensorflow branch.

@rxwei
Copy link
Contributor

rxwei commented Oct 17, 2019

@swift-ci please clean test tensorflow

Copy link
Contributor

@dan-zheng dan-zheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked only utils/update_checkout/update-checkout-config.json, which looks correct.

@asuhan
Copy link
Contributor Author

asuhan commented Oct 17, 2019

No point in merging this, 4ebb910 introduces new merge conflicts.

@dan-zheng
Copy link
Contributor

No point in merging this, 4ebb910 introduces new merge conflicts.

Sorry about that! I don't plan to create any more PRs today.
The GitHub interface suggests there aren't actually merge conflicts though.

@asuhan
Copy link
Contributor Author

asuhan commented Oct 17, 2019

Fixed. There weren't any physical merge conflicts, just broken build because of GenericSignature changes from pointer to value.

@rxwei
Copy link
Contributor

rxwei commented Oct 17, 2019

@swift-ci please clean test tensorflow

2 similar comments
@rxwei
Copy link
Contributor

rxwei commented Oct 17, 2019

@swift-ci please clean test tensorflow

@rxwei
Copy link
Contributor

rxwei commented Oct 17, 2019

@swift-ci please clean test tensorflow

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.