Saleem Abdulrasool

No, I had only seen this with NIO and I shelved it again due to the difficulty of getting the changes merged.

@hiraditya, `-fno-split-cold-code` does workaround the issue. You can likely follow the build here: https://github.com/compnerd/swift-build/blob/main/.github/workflows/swift-toolchain.yml#L1274-L1296 Disabling the bindings should allow you to build without the Swift compiler.

[SourceMgr-7d4fb7.zip](https://github.com/apple/swift-llbuild/files/11094484/SourceMgr-7d4fb7.zip) ``` Function has token parameter but isn't an intrinsic call void @"?AddIncludeFile@SourceMgr@llvm@@QEAAIAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@VSMLoc@2@AEAV34@@Z.cold.1"(ptr %NewBufOrErr, token %51) #33, !dbg !8335 in function ?AddIncludeFile@SourceMgr@llvm@@QEAAIAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@VSMLoc@2@AEAV34@@Z fatal error: error in backend: Broken function found,...

No, the underlying issue is LLDB, not Swift. There has been no one who has stepped up to help work on LLDB, so this is still not available.

@dharmatech correct. `swift ...` is running the swift file as a script, which runs it through the interpreter, which is using LLDB. `swift` compiles the code, doesn't interpret it.

At least on Windows, Foundation is critical to the toolchain itself - the driver and SPM depend on Foundation pretty heavily due to `URL`, `FileManager`, and `Process` at the very...

@swift-ci please build toolchain Windows platform

@swift-ci please build toolchain Windows platform

@swift-ci please build toolchain Windows platform

@swift-ci please build toolchain Windows platform