Skip to content

utils: Unify Debug Format handling in build.ps1#88412

Open
Steelskin wants to merge 1 commit intoswiftlang:mainfrom
Steelskin:fabrice/debug-format-unification
Open

utils: Unify Debug Format handling in build.ps1#88412
Steelskin wants to merge 1 commit intoswiftlang:mainfrom
Steelskin:fabrice/debug-format-unification

Conversation

@Steelskin
Copy link
Copy Markdown
Contributor

Previously, it was possible to specify different debug formats for C/C++ and Swift code. In practice, binaries with both C/C++ and Swift code would end up only having one format over the other, depending on the exact project configuration. Since there is little value in having separate debug information format, this changes the build configuration to only have one debug format for both C/C++ and Swift code.

This also changes the default debug format to codeview. This is because some of the toolchain binaries now exceed 4 GiB of dwarf debug information, resulting in a build failure.

Previously, it was possible to specify different debug formats for C/C++
and Swift code. In practice, binaries with both C/C++ and Swift code
would end up only having one format over the other, depending on the
exact project configuration. Since there is little value in having
separate debug information format, this changes the build configuration
to only have one debug format for both C/C++ and Swift code.

This also changes the default debug format to codeview. This is because
some of the toolchain binaries now exceed 4 GiB of dwarf debug
information, resulting in a build failure.
@Steelskin
Copy link
Copy Markdown
Contributor Author

@swift-ci please build toolchain windows platform

@Steelskin
Copy link
Copy Markdown
Contributor Author

@swift-ci please test windows platform

@Steelskin
Copy link
Copy Markdown
Contributor Author

@swift-ci please smoke test

@Steelskin Steelskin marked this pull request as ready for review April 14, 2026 16:14
@Steelskin Steelskin requested a review from a team as a code owner April 14, 2026 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants