← Back to context

Comment by astrange

3 years ago

Swift's compiler elides obviously useless RC operations at compile time. It doesn't do anything at runtime though.

6 comments

astrange

Reply
vlovich123  3 years ago

That is correct. Like Objective-C the compiler statically removes ARC when it can prove it doesn’t need it (or when you annotate it because where you’re getting it from is manually managing and giving you ownership of the reference). So within a function or cross function with LTO (although it looks like swift doesn’t yet have LTO [1] so I’m not sure about cross-module optimizations).

> When receiving a return result from such a function or method, ARC releases the value at the end of the full-expression it is contained within, subject to the usual optimizations for local values.

Quote from [2] (section 6 has the full details about optimizations). I believe [3] might be the compiler pass.

There actually is some elision that happens at runtime if you install an autoreleasepool if I recall correctly.

I did actually work at Apple so that’s where my recollection comes from although it’s been 8 years since then and I didn’t work on the compiler side of things so my memory could be faulty.

[1] https://github.com/apple/swift/pull/32233

[2] https://opensource.apple.com/source/lldb/lldb-112/llvm/tools...

[3] https://llvm.org/doxygen/group__ARCOpt.html

  • astrange  3 years ago

    > So within a function or cross function with LTO (although it looks like swift doesn’t yet have LTO [1] so I’m not sure about cross-module optimizations).

    I'm not sure Swift supports "static library modules" so in practice any linked object consists of a single module.

    > There actually is some elision that happens at runtime if you install an autoreleasepool if I recall correctly.

    There is a trick in the ObjC ABI that elides autorelease-returns, but it's deterministic after compilation time so I wouldn't call it a runtime optimization.

    • vlovich123  3 years ago

      Correct. But it’ll do it within functions in the same module.

      > but it's deterministic after compilation time so I wouldn't call it a runtime optimization.

      What do you mean? My understanding is that autoreleasepool is 100% at runtime. The compiler is not involved afaik except to know to register autorelease with the currently installed pool.

      2 replies →