[release/dev18.3] Use command line checksumAlgorithm in generator driver#81954
Merged
RikkiGibson merged 8 commits intorelease/dev18.3from Jan 12, 2026
Merged
Conversation
github-actions
bot
force-pushed
the
backport/pr-81934-to-release/dev18.3
branch
from
5339ed9 to
53e0a32
Compare
phil-allen-msft
approved these changes
Jan 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #81934 to release/dev18.3
/cc @RikkiGibson
Customer Impact
Today users are finding that source generated files can use a different checksum algorithm in PDBs than ordinary files use in the same compilation. Prior to this change, there's no way for source generator users to control which checksum algorithm is used for the generated files. This is problematic because certain builds need to restrict which checksum algorithms are permitted to be used or not.
This change makes it so the same checksum algorithm determined by compiler options will be used for all files in the compilation, both ordinary and source-generated.
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
Automated tests are included for the scenario. The issue was already known for a few years, but not thought to be blocking until recently.
Risk
Low. We consider it unlikely that components downstream of the generated files are relying on a generator-determined checksum algorithm, instead of one determined by compiler options.