Our compiler can compile for man hy different platforms, including native code for Windows, Linux, all the Apple OSs and Android NDK, in addition to WebAssembly, .NET and Java/JVM/Android SDK (lea latter two, .NET and JVM being “managed” platforms with byte code.
In all cases, you can expect top of the line performance out of the generated code. In particular, I want to make the point that the difference between “native” and “managed” often gets over-exaggerated. In our experience, well-written .NET code, for example, will run as performant as well written code compiled “natively” for the CPU type/OS. it’s a misconception that managed code runs slow and “interpreted”, really 
We don’t do any comparisons or benchmarks for that ourselves, but for the Apple/Cocoa platform, I would expect code for our compiler to be faster and actually be “more native” that Apple’s — especially when interacting with Cocoa APIs (as most Mac or iOS apps are won’t to do eventually ;).
Apple had a pretty scary talk about Swift performance issues at WWDC, (iirc) last year…