-
Notifications
You must be signed in to change notification settings - Fork 51
Undefine MBEDTLS_MPI_MAX_SIZE #220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Just a minor note: merging ARMmbed/mbed-os#8936 will not actually cause trouble until the next Mbed TLS update in the Mbed OS. |
Correct, I explained it wrong |
@@ -33,6 +33,9 @@ | |||
* Set this value higher to enable handling larger keys, but be aware that this | |||
* will increase the stack usage. | |||
*/ | |||
#if defined(MBEDTLS_MPI_MAX_SIZE) | |||
#undef MBEDTLS_MPI_MAX_SIZE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should be able to unconditionally undef
this. There are no warnings if it isn't defined, right?
Undefine `MBEDTLS_MPI_MAX_SIZE` in case it is already defined in the configuration file.
8b17022
to
0b991cb
Compare
@Patater I changed according to your comment, in the same commit, as the change is minimal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I liked the ifdeffed version a bit more, but it is still correct and, apparently, popular, so LGTM
I can understand this PR is required within the constraints of the current configuration system, but I think |
retest |
Undefine
MBEDTLS_MPI_MAX_SIZE
in case it is already definedin the configuration file.
This should avoid compilation warnings and unintended behaviour, once ARMmbed/mbed-os#8936 will be merged