[5.x] Eliminate compiler warnings and enable warnings-as-errors in CI#447
Draft
simonjbeaumont wants to merge 4 commits into
Draft
[5.x] Eliminate compiler warnings and enable warnings-as-errors in CI#447simonjbeaumont wants to merge 4 commits into
simonjbeaumont wants to merge 4 commits into
Conversation
simonjbeaumont
force-pushed
the
sb/warnings-free
branch
from
dee5ce1 to
9658064
Compare
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
1 participant
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.
Motivation:
The build currently produces a number of complier warnings. We can address these and lock in the win by enabling warnings-as-errors in CI.
Modifications:
CheckImplementationOnlylanguage featureshorten-64-to-32warnings in BoringSSL targetvendored-sources.txtto excludesResult:
Project now builds without warnings.