building swift bundler on windows failed

[syriku]

crashed when running swift build -c release (even debug mode)

here is the log

PS C:\Users\username\Documents\swift-bundler> swift build -c release
[1/1] Planning build
Building for production...
error: compile command failed due to exception 3 (use -v to see invocation)
SIL verification failed: witness table entry for #ErrorHandledCommand.wrappedValidate must be ABI-compatible
  Different error result conventions
  @convention(witness_method: ErrorHandledCommand) (@in_guaranteed BundleCommand) -> @error RichError<SwiftBundlerError>
  @convention(witness_method: ErrorHandledCommand) <τ_0_0 where τ_0_0 : ErrorHandledCommand> (@in_guaranteed τ_0_0) -> @error_indirect RichError<τ_0_0.ErrorMessage>
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace.
Stack dump:
0.      Program arguments: C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Toolchains\\6.2.0+Asserts\\usr\\bin\\swift-frontend.exe -frontend -c -filelist C:\\Users\\username\\AppData\\Local\\Temp\\TemporaryDirectory.jCREQJ\\sources-1 -supplementary-output-file-map C:\\Users\\username\\AppData\\Local\\Temp\\TemporaryDirectory.jCREQJ\\supplementaryOutputs-1 -target x86_64-unknown-windows-msvc -disable-objc-interop -sdk C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Platforms\\6.2.0\\Windows.platform\\Developer\\SDKs\\Windows.sdk\\ -I C:\\Users\\username\\Documents\\swift-bundler\\.build\\x86_64-unknown-windows-msvc\\release\\Modules-tool -I C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Platforms\\6.2.0\\Windows.platform\\Developer\\Library\\XCTest-6.2.0\\usr\\lib\\swift\\windows -I C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Platforms\\6.2.0\\Windows.platform\\Developer\\Library\\XCTest-6.2.0\\usr\\lib\\swift\\windows\\x86_64 -I C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Platforms\\6.2.0\\Windows.platform\\Developer\\Library\\Testing-6.2.0\\usr\\lib\\swift\\windows -color-diagnostics -Xcc -fcolor-diagnostics -g -debug-info-format=dwarf -dwarf-version=4 -module-cache-path C:\\Users\\username\\Documents\\swift-bundler\\.build\\x86_64-unknown-windows-msvc\\release\\ModuleCache -static -swift-version 5 -O -D SWIFT_PACKAGE -D SWIFT_MODULE_RESOURCE_BUNDLE_UNAVAILABLE -load-plugin-executable C:\\Users\\username\\Documents\\swift-bundler\\.build\\x86_64-unknown-windows-msvc\\release\\CasePathsMacros-tool.exe#CasePathsMacros -enable-upcoming-feature FullTypedThrows -empty-abi-descriptor -file-compilation-dir C:\\Users\\username\\Documents\\swift-bundler -Xcc -fmodule-map-file=C:\\Users\\username\\Documents\\swift-bundler\\.build\\x86_64-unknown-windows-msvc\\release\\CTOML-tool.build\\module.modulemap -Xcc -I -Xcc C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\TOMLKit\\Sources\\CTOML\\include -Xcc -fmodule-map-file=C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\Yams\\Sources\\CYaml\\include\\module.modulemap -Xcc -I -Xcc C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\Yams\\Sources\\CYaml\\include -Xcc -fmodule-map-file=C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-crypto\\Sources\\CCryptoBoringSSLShims\\include\\module.modulemap -Xcc -I -Xcc C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-crypto\\Sources\\CCryptoBoringSSLShims\\include -Xcc -fmodule-map-file=C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-crypto\\Sources\\CCryptoBoringSSL\\include\\module.modulemap -Xcc -I -Xcc C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-crypto\\Sources\\CCryptoBoringSSL\\include -Xcc -fmodule-map-file=C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-syntax\\Sources\\_SwiftSyntaxCShims\\include\\module.modulemap -Xcc -I -Xcc C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-syntax\\Sources\\_SwiftSyntaxCShims\\include -Xcc -fmodule-map-file=C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-atomics\\Sources\\_AtomicsShims\\include\\module.modulemap -Xcc -I -Xcc C:\\Users\\username\\Documents\\swift-bundler\\.build\\checkouts\\swift-atomics\\Sources\\_AtomicsShims\\include -Xcc -D_MT -Xcc -D_DLL -Xcc -Xclang -Xcc --dependent-lib=msvcrt -Xcc -gdwarf -no-auto-bridging-header-chaining -module-name SwiftBundler -package-name swift_bundler -in-process-plugin-server-path C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Toolchains\\6.2.0+Asserts\\usr\\bin\\SwiftInProcPluginServer.dll -plugin-path C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Toolchains\\6.2.0+Asserts\\usr\\bin -plugin-path C:\\Users\\username\\AppData\\Local\\Programs\\Swift\\Toolchains\\6.2.0+Asserts\\usr\\local\\bin -autolink-library oldnames -autolink-library msvcrt -Xcc -D_MT -Xcc -D_DLL -enable-default-cmo -parse-as-library -num-threads 32 -output-filelist C:\\Users\\username\\AppData\\Local\\Temp\\TemporaryDirectory.jCREQJ\\outputs-1
1.      Swift version 6.2-dev (LLVM 0bbdf73817e84bd, Swift 5797130e90a66c5)
2.      Compiling with effective version 5.10
3.      While evaluating request ASTLoweringRequest(Lowering AST to SIL for module SwiftBundler)
Exception Code: 0x80000003
 #0 0x00007ff7d41e59d5 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x6f059d5)
 #1 0x00007ffe93cf1989 (C:\WINDOWS\System32\ucrtbase.dll+0xc1989)
 #2 0x00007ffe93cd4ab1 (C:\WINDOWS\System32\ucrtbase.dll+0xa4ab1)
 #3 0x00007ff7cea0cc6b (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x172cc6b)
 #4 0x00007ff7cea0ad53 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x172ad53)
 #5 0x00007ff7cea0f68f (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x172f68f)
 #6 0x00007ff7cea0df92 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x172df92)
 #7 0x00007ff7cea0e48c (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x172e48c)
 #8 0x00007ff7ce02e59c (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0xd4e59c)
 #9 0x00007ff7ce03561b (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0xd5561b)
#10 0x00007ff7ce03cb46 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0xd5cb46)
#11 0x00007ff7ce02b4a3 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0xd4b4a3)
#12 0x00007ff7ce03b154 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0xd5b154)
#13 0x00007ff7cd927ac6 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x647ac6)
#14 0x00007ff7cd926a54 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x646a54)
#15 0x00007ff7cd926f0b (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x646f0b)
#16 0x00007ff7cd928e72 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x648e72)
#17 0x00007ff7cd774050 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x494050)
#18 0x00007ff7cd773be7 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x493be7)
#19 0x00007ff7d42454b8 (C:\Users\username\AppData\Local\Programs\Swift\Toolchains\6.2.0+Asserts\usr\bin\swift-frontend.exe+0x6f654b8)
#20 0x00007ffe948be8d7 (C:\WINDOWS\System32\KERNEL32.DLL+0x2e8d7)
#21 0x00007ffe96b3c34c (C:\WINDOWS\SYSTEM32\ntdll.dll+0x3c34c)

[bbrk24]

"SIL verification failed" indicates a bug in Swift itself, right? If that's the case there may be minimal recourse here, beyond a very obscure workaround by restructuring the offending part of the code.

[syriku]

"SIL verification failed" indicates a bug in Swift itself, right? If that's the case there may be minimal recourse here, beyond a very obscure workaround by restructuring the offending part of the code."

maybe I can try to use an old version of swift?

[stackotter]

Man that one part of the codebase has caused so many distinct compiler crashes since I updated everything to use typed throws. I haven’t seen this exact crash before.

Interestingly, all previously known crashes in this area of the code weren’t reproducible with Swift 6.2, and I notice that your bug is happening with 6.2 (although dev). Also the previous crashes were generally release only.

Maybe try with the toolchain that Swift Bundler’s Windows CI uses? (6.1-RELEASE)

[syriku]

Man that one part of the codebase has caused so many distinct compiler crashes since I updated everything to use typed throws. I haven’t seen this exact crash before.

Interestingly, all previously known crashes in this area of the code weren’t reproducible with Swift 6.2, and I notice that your bug is happening with 6.2 (although dev). Also the previous crashes were generally release only.

Maybe try with the toolchain that Swift Bundler’s Windows CI uses? (6.1-RELEASE)

Thank you for reply.
I have tried to use Swift 6.1.2 (the newest release version) and meet this error so I updated to Swift 6.2(dev). Maybe I can try 6.1

[syriku]

Man that one part of the codebase has caused so many distinct compiler crashes since I updated everything to use typed throws. I haven’t seen this exact crash before.

Interestingly, all previously known crashes in this area of the code weren’t reproducible with Swift 6.2, and I notice that your bug is happening with 6.2 (although dev). Also the previous crashes were generally release only.

Maybe try with the toolchain that Swift Bundler’s Windows CI uses? (6.1-RELEASE)

I tried 6.1 and got an error again with a different log message.

Assertion failed: index < getNumSILArguments(), file C:\Users\swift-ci\jenkins\workspace\swift-6.1-windows-toolchain\swift\lib\SIL\IR\SILArgument.cpp, line 91
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace.

But this time I got success when I built a debug version swift build.

[stackotter]

Ok that's good to hear! A debug build should be ok because most of the time Swift Bundler just orchestrates other tools or does file system operations (so release doesn't affect things much). I'll keep this issue open because it's still something that I want to resolve eventually.

It may be possible to refactor the code slightly to avoid the compiler crash, but ideally we want to get this crash fixed upstream in the compiler.

If you feel comfortable doing so and/or have the time, it'd be great if you could attempt to create a minimal reproducer for the compiler crash.

[syriku]

Ok that's good to hear! A debug build should be ok because most of the time Swift Bundler just orchestrates other tools or does file system operations (so release doesn't affect things much). I'll keep this issue open because it's still something that I want to resolve eventually.

It may be possible to refactor the code slightly to avoid the compiler crash, but ideally we want to get this crash fixed upstream in the compiler.

If you feel comfortable doing so and/or have the time, it'd be great if you could attempt to create a minimal reproducer for the compiler crash.

Nice. I'd like to try it