Skip to content

Fix a gcc-10 warning#11393

Closed
bernd-edlinger wants to merge 1 commit intoopenssl:masterfrom
bernd-edlinger:fix_gcc_10_warning
Closed

Fix a gcc-10 warning#11393
bernd-edlinger wants to merge 1 commit intoopenssl:masterfrom
bernd-edlinger:fix_gcc_10_warning

Conversation

@bernd-edlinger
Copy link
Member

Use memcpy when zero-termination is not requred
to make it explict for the compiler to see what
we are doing here.

Fixes #11392

Checklist
  • documentation is added or updated
  • tests are added or updated

Use memcpy when zero-termination is not requred
to make it explict for the compiler to see what
we are doing here.

Fixes openssl#11392
@bernd-edlinger
Copy link
Member Author

bernd-edlinger commented Mar 24, 2020

typo in the commit message "required" will fix that when merging. note to myself,

@levitte levitte added approval: done This pull request has the required number of approvals branch: master Applies to master branch branch: 1.1.1 Applies to OpenSSL_1_1_1-stable branch (EOL) labels Mar 24, 2020
@levitte
Copy link
Member

levitte commented Mar 24, 2020

I've assumed this should be cherry picked to 1.1.1 as well and labled accordingly.

@bernd-edlinger
Copy link
Member Author

Oh, long time ago that I looked at 1.1.1

@bernd-edlinger
Copy link
Member Author

1.1.1 does not seem to be affected.

@openssl-machine
Copy link
Collaborator

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually.

@t8m t8m added approval: ready to merge The 24 hour grace period has passed, ready to merge and removed approval: done This pull request has the required number of approvals branch: 1.1.1 Applies to OpenSSL_1_1_1-stable branch (EOL) labels Mar 25, 2020
@bernd-edlinger
Copy link
Member Author

Oh, no who did change the strncpy that change is not okay.
Now I have a merge conflict.

@DDvO
Copy link
Contributor

DDvO commented Mar 26, 2020

The fix was semantically wrong anyway.

@DDvO
Copy link
Contributor

DDvO commented Mar 26, 2020

Oh, meanwhile I realize it was not wrong, sorry for the confusion.
Yet it was not semantically needed since in the end the NUL termination is guaranteed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approval: ready to merge The 24 hour grace period has passed, ready to merge branch: master Applies to master branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

building with gcc-10 gives warning/error

5 participants