commit | 38c7b224ce22c25fed04007839edf974bd13439d | [log] [tgz] |
---|---|---|
author | Linus Torvalds <torvalds@linux-foundation.org> | Fri Nov 30 14:45:01 2018 -0800 |
committer | Linus Torvalds <torvalds@linux-foundation.org> | Fri Nov 30 14:45:01 2018 -0800 |
tree | 036a6170d809343dbd5969efbc937667398b56bb | |
parent | b6839ef26e549de68c10359d45163b0cfb031183 [diff] |
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>