@swift-ci create

Comment by Jorge Mendez (JIRA)

@jckarter any updates on the internal prioritization of this regression? Disabling -Osize translates to a ~1MB binary size regression on our end and it's preventing us from upgrading to Xcode 11.4.

Thanks!

Fixed here: #31175

You might be able to workaround the issue by marking the function(s) triggering the issue with ``@_optimize(speed)``.

For example in the attached test case

class CrashSwiftOptimizerTests: XCTestCase {
    @_optimize(speed)
    func testOSize() {

Comment by Jorge Mendez (JIRA)

aschwaighofer@apple.com (JIRA User) thanks for the workaround. Apart from disabling -Osize entirely, is there another workaround that we can apply globally? Annotating on a per function basis is not truly feasible for us.

There is a way to disable a specific pass. The problematic pass is the Outliner: ``-Xllvm -sil-disable-pass=Outliner``. You could try adding this flags under "Other Swift Flags" in the build settings.