Page MenuHomeFreeBSD

[libc][NFC] Split definitions of memcpy and memmove
Needs ReviewPublic

Authored by gfunni234_gmail.com on Aug 24 2021, 5:42 PM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 22 2023, 9:34 PM
Unknown Object (File)
Dec 13 2023, 12:07 AM
Unknown Object (File)
Nov 22 2023, 7:15 AM
Unknown Object (File)
Nov 15 2023, 12:49 PM
Unknown Object (File)
Nov 10 2023, 10:00 PM
Subscribers
None

Details

Reviewers
imp
jrtc27
dim
Summary

Memmove is a valid way to implement memcpy. However, memcpy isn’t a valid way to implement memmove.

For this reason, I split the definitions into two. No ABI breakage should occur

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

gfunni234_gmail.com created this revision.
gfunni234_gmail.com retitled this revision from Split definitions of memcpy and memmove to [libc][NFC] Split definitions of memcpy and memmove.

Your description is not what this does for userspace. It is what it does for the kernel but that is bad, now we have two copies of basically the same thing in one file.