# Compiler performance overhead of assertions and SIL verifier

**URL:** <https://forums.swift.org/t/compiler-performance-overhead-of-assertions-and-sil-verifier/42983>\
**Category:** Compiler\
**Created:** [December 17, 2020, 6:09pm UTC](https://forums.swift.org/t/compiler-performance-overhead-of-assertions-and-sil-verifier/42983 "2020-12-17T18:09:13Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![dan-zheng](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/dan-zheng/32/2534_2.png) [@dan-zheng](https://forums.swift.org/u/dan-zheng)\
**Post date:** [December 18, 2020, 11:48pm UTC](https://forums.swift.org/t/compiler-performance-overhead-of-assertions-and-sil-verifier/42983/12 "2020-12-18T23:48:58Z")

</div>

> [@Michael\_Gottesman](#):
>
> I am assuming you are talking about [swift.org](http://swift.org) builds (where I believe we have autodiff now)? Or builds built another way?

Yes - all code for differentiable programming in Swift has been upstreamed to `main` (done for a few months now), where development continues.

About Swift for TensorFlow: S4TF is switching to build using [Swift.org - Download Swift](http://swift.org/download) toolchains instead of custom ones from [`tensorflow` branch](https://github.com/apple/swift/tree/tensorflow). This effort is in progress and is almost done! (See recent [tensorflow/swift-apis](https://github.com/tensorflow/swift-apis) PRs about "migrating to standard/stock toolchains".)

This means "de-forking Swift for TensorFlow" for good, which should allow Swift for TensorFlow developers and users to leverage all the tooling and infra for `apple/swift:main` branch, like [Swift.org - Download Swift](http://swift.org/download) toolchains and [ci.swift.org](http://ci.swift.org) artifacts (continuous assert snapshots) for all supported platforms. 🥳

---

_[View the full topic](https://forums.swift.org/t/compiler-performance-overhead-of-assertions-and-sil-verifier/42983)._