swiftlang / swift

The Swift Programming Language
https://swift.org
Apache License 2.0
67.58k stars 10.36k forks source link

[SR-9993] Crash when attempting to build Swift toolchain #52397

Open swift-ci opened 5 years ago

swift-ci commented 5 years ago
Previous ID SR-9993
Radar None
Original Reporter aemino (JIRA User)
Type Bug

Attachment: Download

Environment Arch Linux (4.20.10-arch1-1-ARCH)
Additional Detail from JIRA | | | |------------------|-----------------| |Votes | 0 | |Component/s | | |Labels | Bug, BuildScript, Linux | |Assignee | None | |Priority | Medium | md5: 7c759a7c99e95931845587296dfee098

Issue Description:

I have been successfully using a development snapshot of the Swift toolchain built on Arch Linux since December 2018 (about 2 months ago). I recently attempted to build a newer toolchain, (snapshot-2019-02-14), but I am no longer able to do so seemingly due to a crash when building IndexStoreDB.

I am building the toolchain using the build script and a very slightly modified version of the buildbot_linux preset that patches the Python version to 2.

belkadan commented 5 years ago

"fatal error: error in backend: invalid llvm.linker.options" I wonder what the invalid options are. Can you run that failing command with "-S -emit-llvm -o out.ll" appended to the end? That'll generate the LLVM IR for the problem file and we can see what's going on.

(It's likely this is a Clang bug and will need to be reported at https://llvm.org/bugs, but let's figure it out.)

swift-ci commented 5 years ago

Comment by aemino (JIRA)

I've attached the `out.ll` file to this issue as you requested.

As an aside, it might be worth noting that when trying to build SourceKit-LSP in the past (which depends on IndexStoreDB), I had to prepend "env CCC_OVERRIDE_OPTIONS="#x-fmodules s/-fmodules-cache-path.*//"" to the `swift build` invocation in order for it to compile successfully. Not sure if there's any relation between these, just wanted to point it out in case.

swift-ci commented 5 years ago

Comment by aemino (JIRA)

Hey @belkadan, would you mind taking a look at this issue again?