Ensure dst_vec is initialized after init_copy() #2170
Merged
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.
Address the following compiler warnings which are causing
hardened-compiletask failure:This appears to be due to the
init_copy()function containing code paths which may fail to initialize*dst_vec(when either reservation or element copy fails). This can leave*dst_vecwith indeterminate values which are subsequently accessed by test assertions.This PR proposes always leaving
*dst_vecin a (zero-)initialized state even on failure to address these warnings and potential UB.