Linus Torvalds 38c7b224ce unifdef: use memcpy instead of strncpy ...

New versions of gcc reasonably warn about the odd pattern of

	strncpy(p, q, strlen(q));

which really doesn't make sense: the strncpy() ends up being just a slow
and odd way to write memcpy() in this case.

There was a comment about _why_ the code used strncpy - to avoid the
terminating NUL byte, but memcpy does the same and avoids the warning.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

2018-11-30 14:45:01 -08:00

35 KiB

Raw Blame History

View Raw