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.
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.
On Dec 4, 2015, at 5:27 AM, Alex Blewitt <alex.blewitt@gmail.com> wrote:
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.
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.
The presentation I gave at QCon London 2016 where I talked about SIL Inspector has now been published on InfoQ:
Alex
···
On 4 Dec 2015, at 13:27, Alex Blewitt <alex.blewitt@gmail.com> wrote:
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.
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.