Protocol Extensions May Crash Swift Compiler when Whole-Module Optimization is Enabled

Originator:Czechnmail
Number:rdar://24547884 Date Originated:08 Feb 2016
Status:Open Resolved:No
Product:Xcode Product Version:7.2.1
Classification:Crash/Hang/Data Loss Reproducible:Always
 
When extending a protocol bridged from Objective-C and using self in the extension method, the Swift compiler may crash with a segmentation fault if whole module optimization is enabled. The issue was originally reported to the major open-source framework at https://github.com/facebook/AsyncDisplayKit/issues/1109 .

I've attached a reduced project (edit: https://github.com/Adlai-Holler/ASDKWMOTest ) that reliably crashes the compiler both Xcode 7.2.1 and 7.3 Beta 2.

Steps to Reproduce:
Attempt to build the project under Xcode 7.2.1 or 7.3 Beta 2.

Expected Results:
The project builds.

Actual Results:
The Swift compiler crashes and a build error is generated.

Version:
7.2.1 and 7.3 beta 2

Comments

Has this issue been resolved in the mean time? Are there other issues with Whole Module Optimization?

By fabian.ehrentraud at July 25, 2016, 1:38 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!