With Swift 3 I’ve found these crashes to be indicative of an underlying source issue rather than something random in the compiler. When you get the crash, can you get the backtrace in the Xcode build log? Sometimes that has clues about what it was doing when it crashed. A lot of the time when the crash is during the parsing or SIL generation for one of your functions, it will note it and you can take a look, as there may be a type mismatch.
Jon > On Oct 21, 2016, at 12:26 PM, Evan Maloney via swift-users > <swift-users@swift.org> wrote: > > After a gargantuan effort updating our entire codebase to Swift 3.0, we are > now being greeted with "Segmentation fault: 11" compiler crash whenever > attempting to build. > > The issue seems to be related to generics, and sounds similar to this issue: > > > http://stackoverflow.com/questions/39426535/segmentation-fault-11-xcode-8-swift-3-after-using-notificationcenter/39426812 > > I've filed a bug report that includes our project codebase, which triggers > the issue 100% of the time: > > rdar://problem/28890409 > > The usual work-around of turning off Whole Module Optimization (which has > gotten around a lot of compiler crashes in the past) does not work here. > > Unfortunately, this code is in such a tangle of generics that undoing it is > not going to be simple. Until a new version of Xcode ships, we're pretty much > blocked from using Swift 3.0 unless another work-around is possible. > _______________________________________________ > swift-users mailing list > swift-users@swift.org > https://lists.swift.org/mailman/listinfo/swift-users _______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
