refs/tags/swift-DEVELOPMENT-SNAPSHOT-2016-10-07-a - third_party/swift-clang

tag	7c4505bb6c22ca5ccc46c871cc26167134405a83
tagger	Swift Automation <swift_jenkins@apple.com>	Fri Oct 07 20:11:56 2016 -0500
object	23f1b289cf19f247c9565912a715a2cb23570b52

Tag build swift-DEVELOPMENT-SNAPSHOT-2016-10-07-a

commit	23f1b289cf19f247c9565912a715a2cb23570b52	[log] [tgz]
author	swift-ci <swift-ci@users.noreply.github.com>	Thu Oct 06 17:16:00 2016 -0700
committer	swift-ci <swift-ci@users.noreply.github.com>	Thu Oct 06 17:16:00 2016 -0700
tree	d20194b61126620f0e789d7c7ce09da46e67b1d3
parent	4d079b43591d2455852a2b8b40ee0e6a630b150c [diff]
parent	d015b205aa33c9cb43275cd77c0c1cb142a4d0e0 [diff]

Merge remote-tracking branch 'origin/swift-3.1-branch' into stable

* origin/swift-3.1-branch:
  [modules] Be sure to emit local specializations of imported templates, even if the resulting specialization is not referenced by the rest of the AST. This both avoids performing unnecessary reinstantiations in downstream users of the AST file and fixes a bug (breaking modules self-host right now) where we would sometimes fail to emit a definition of a class template specialization if we imported just a declaration of it from elsewhere (see new testcase for reduced example).

tree: d20194b61126620f0e789d7c7ce09da46e67b1d3