Hi Mark, That's unfortunate. Assuming you're on macOS, do you mind running
ls ~/Library/Logs/DiagnosticReports/swift*.crash that might reveal some compiler crash reports. If yes I think the best would be to file a bug for these crashes on http://bugs.swift.org . What presumably would be most helpful is a small reproduction of that crash but I realise that can be hard at times... Thanks, Johannes > On 7 Apr 2017, at 07:31, Mark Woollard via swift-dev <swift-dev@swift.org> > wrote: > > Following upgrade to Xcode 8.3 / Swift 3.1 I have a project where the > compiler is crashing when Swift optimisation is enabled in release builds > (whole module or single file). Project builds fine for earlier compiler > releases. The crash gives no stack trace in console. The crash occurs for one > framework component within a complex project with multiple frameworks + app > with lots of inter-dependency so its hard to know what specifically is > causing the issue or produce something to reproduce and file with a bug > report. If I turn off optimisation for that one framework the whole project > builds. > > I gather crashes related to optimisation have been seen by others from > discussions I’ve seen elsewhere ? > What is the status of the issue, ETA for a fix ? > Is there anything I can do to help provide info to fix the issue ? I might be > able to build debug version of compiler and try and use it under debugger > with the project for example, or is there anything else I can do to get you > useful info ? > > Thanks > Mark > _______________________________________________ > swift-dev mailing list > swift-dev@swift.org > https://lists.swift.org/mailman/listinfo/swift-dev _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
