New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR-14743] Compiler Crash with Swift 5.4.1/5.5/main on Linux #57093
Comments
I have also create an issue in the OpenAPIKit repo for reference including the complete error log: mattpolzin/OpenAPIKit#224 (comment) |
As pointed out by Mathew Polzin (mattpolzin/OpenAPIKit#224 the following issue seems to track the same problem: https://bugs.swift.org/browse/SR-14680 |
@swift-ci create |
Thank you! Let’s start with @gottesmm who may have an idea if we already know the root cause of this. Or if this needs further diagnosing |
@weissi As noted in your tweet I have checked it with the nightly builds for Swift 5.4 and Swift 5.5: https://github.com/PSchmiedmayer/OpenAPIKit/actions/runs/920890077. The build fails on the nightly builds of Swift 5.4 and Swift 5.5 as well as the nightly builds on the main branch. The builds run fine on macOS. As far as I can see it started failing with Swift 5.4, Swift 5.3 builds seem to be fine. |
One-line repo
my repro with 5.5
|
@swift-ci create |
it's in the SILVerifier
CC @gottesmm |
I am starting to investigate. That being said, @PSchmiedmayer I want to unblock you. Here is a work around: -Xfrontend -sil-verify-none. That should disable the verifier allowing you to build until a fix gets to you. I wouldn't enable it permanently since the verifier makes sure that the compiler is working correctly! |
Nice one @gottesmm, thanks! @PSchmiedmayer to hand the suggested arguments through with SwiftPM, you'll need
|
@PSchmiedmayer thanks![]( Don't forget since otherwise you can run into weird errors potentially. I am just glad that you are unblocked) |
@weissi @gottesmm Polzin (JIRA User) Is there any update on this issue? I might come across as pushy here but I really like OpenAPIKit and think it is crucial for growing Server-Side Swift ecosystem. While the workaround is fine for now it would be great if an Swift 5.4.X patch or latest Swift 5.5 would resolve the issue so we and other maintainers can easily use and integrate the project. Otherwise the hurdle of using the project would be quite large as developers guided from the Swift Server Work Group projects page probably won't dig too deep on a first try to discover the workaround. I am definitely not a compiler expert and am not familiar with C++ but if there is any other way I can help or assist to fix the problem I am happy to invest time and help! |
Attachment: Download
Environment
Swift version 5.4.1 (swift-5.4.1-RELEASE)
Additional Detail from JIRA
md5: 266c7db5493fbd8ee70a23c0557b75ed
duplicates:
Issue Description:
Dear Swift compiler team, dear Swift open source community,
while updating a Server-Side Swift package to Swift 5.4 (Apodini/Apodini#294 I have noted that a dependency of the project (OpenAPIKit) fails to compile on Swift 5.4 on Linux resulting in a compiler crash.
The compiler crashes with the error log attached below.
You can reproduce the error as follows:
Clone the OpenAPIKit repo (OpenAPIKit) to your machine
Open your terminal and navigate in the root OpenAPIKit folder you cloned the repo in
Start up a docker container with the latest Swift docker image and mount the folder in the docker container: `docker run -ti -v $(pwd):/OpenAPIKit swift`
After the image is pulled you can execute commands in the Docker image. `cd` in the `OpenAPIKit` folder and run `swift build`
You receive the following error log and a hint to create a bug report on bugs.swift.org: ErrorLog.txt
These are the last lines of the error log:
I have also added additional GitHub Actions to my fork at https://github.com/PSchmiedmayer/OpenAPIKit. You can see that all Swift 5.4 related builds fail: https://github.com/PSchmiedmayer/OpenAPIKit/actions/runs/919770569.
Feel free to reach out to me if you have any follow up questions and already a huge thanks to anyone from the Swift compiler team and/or from the Swift open source community for taking a look at the issue.
The text was updated successfully, but these errors were encountered: