summaryrefslogtreecommitdiff
path: root/win32/config.gc
diff options
context:
space:
mode:
authorAaron Crane <arc@cpan.org>2017-10-12 13:47:22 +0200
committerAaron Crane <arc@cpan.org>2017-10-21 16:51:21 +0100
commit1c1d7d5ba0bc33e7bea0a9aeb2d420fc5a8128ab (patch)
tree74492a42f48126a77646de9420baebc6c28041bf /win32/config.gc
parent04322328fc4bc2863d0bc74339ed92d33b7eaba7 (diff)
downloadperl-1c1d7d5ba0bc33e7bea0a9aeb2d420fc5a8128ab.tar.gz
Don't look for a "safe" memcpy()
C89 says that, if you want to copy overlapping memory blocks, you must use memmove(), and that attempt to copy overlapping memory blocks using memcpy() yields undefined behaviour. So we should never even attempt to probe for a system memcpy() implementation that just happens to handle overlapping memory blocks. In particular, the compiler might compile the probe program in such a way that Configure thinks overlapping memcpy() works even when it doesn't. This has the additional advantage of removing a Configure probe that needs to execute a target-platform program on the build host.
Diffstat (limited to 'win32/config.gc')
-rw-r--r--win32/config.gc1
1 files changed, 0 insertions, 1 deletions
diff --git a/win32/config.gc b/win32/config.gc
index 8863d11943..58882d93d0 100644
--- a/win32/config.gc
+++ b/win32/config.gc
@@ -461,7 +461,6 @@ d_rint='undef'
d_rmdir='define'
d_round='undef'
d_safebcpy='undef'
-d_safemcpy='undef'
d_sanemcmp='define'
d_sbrkproto='undef'
d_scalbn='undef'