Implement workaround for FORTIFY_SOURCE warning with jitterentropy #2728
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.
Issues:
Resolves #2725
Description of changes:
We have received several reports where users are required to workaround compilation issues with v1.60.0+ releases of AWS-LC where we re-introduced jitterentropy into the library. This silences the associated fortify source warnings if FORTIFY_SOURCE is enabled, as the
-O0optimization flag, required by jitterentropy's design, is not compatible with it.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.