dp_rte_flow_helpers: Explicit array initialization#779
Closed
mkalcok wants to merge 1 commit into
Closed
Conversation
GCC 15 introduces 'unterminated-string-initialization'[0] warning and since we treat warning as errors in our builds, we might as well get ahead of the issue and change from string literals to explicit array initialization. [0] https://gcc.gnu.org/cgit/gcc/commit/?id=44c9403ed1833ae71a59e84f9e37af3182be0df5 Signed-off-by: Martin Kalcok <martin.kalcok@sap.com>
Author
|
PR from fork seems to cause problems in CI. |
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.
GCC 15 introduces 'unterminated-string-initialization'[0] warning and since we treat warning as errors in our builds, we might as well get ahead of the issue and change from string literals to explicit array initialization.
[0] https://gcc.gnu.org/cgit/gcc/commit/?id=44c9403ed1833ae71a59e84f9e37af3182be0df5
Proposed Changes