Open aciidgh opened 8 years ago
I'm...not sure things are set up such that we can deserialize new declarations during optimization passes, but I wouldn't expect it to outright fail.
is there a workaround to avoid this crash for now?
Without looking into it, it's hard to even say what's wrong. Unless PathImpl got removed from Basic or something.
nah its there and compiles without -O flag
I don't know why but changing PathImpl (Basic/Path.swift) from private to internal fixes the issue.
Is this still an issue?
Not for package manager because of the workaround. Will see if I can figure out a smaller test case for compiler
Created a very small test case.
Unzip the crash.zip file and run
$ swift build -c release -Xswiftc -enable-testing
@swift-ci create
I stumbled upon the TODO in SwiftPM to fix this. I tested it and the Crash.zip, both were able to build without issue using the latest trunk toolchain (DEVELOPMENT-SNAPSHOT-2018-10-03-a).
I have opened [this|https://github.com/apple/swift-package-manager/pull/1817] pull request making this private again.
Attachment: Download
Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | Compiler | |Labels | Bug, CompilerCrash, OptimizedOnly | |Assignee | None | |Priority | Medium | md5: 17b33f53a24ac42c15604a8c190e2c26Issue Description:
There seems to be this compiler crash while building the module "PackageLoadingTests" of SwiftPM with "-O" flag
How to reproduce:
$ xcrun --find swiftc
/Library/Developer/Toolchains/swift-DEVELOPMENT-SNAPSHOT-2016-10-18-a.xctoolchain/usr/bin/swiftc
$ git clone -b release-testable https://github.com/aciidb0mb3r/swift-package-manager.git
$ cd swift-package-manager
$ Utilities/bootstrap --release