<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I wrote a small utility SILInspector [1] (which wraps around the output of xcrun swiftc -emit-sil and friends) for my presentation at GotoCon Berlin yesterday [2]. It’s primarily a tool that’s useful for seeing what gets generated by each stage of the pipeline and (for example) showing how in-lining optimisations can lead to further optimisations resulting in functions being completely excluded in compiled output.<div class=""><br class=""></div><div class="">It might be of interest to those experimenting with the compiler and/optimisations, although as I said, there’s nothing that can’t be done from the command line.</div><div class=""><br class=""></div><div class="">Alex</div><div class=""><br class=""></div><div class="">[1] <a href="https://github.com/alblue/SILInspector" class="">https://github.com/alblue/SILInspector</a></div><div class="">[2] <a href="https://speakerdeck.com/alblue/swift-2-under-the-hood-gotober-2015" class="">https://speakerdeck.com/alblue/swift-2-under-the-hood-gotober-2015</a> </div></body></html>