memcpy vs. CopyMemory

Straight out of WINBASE.H

#define CopyMemory RtlCopyMemory

Then, straight out of WINNT.H

#define RtlCopyMemory(Destination,Source,Length) memcpy((Destination),(Source),(Length))

Don''t worry about it.

When you use CopyMemory, you''re using memcpy. There is no difference.

This is a good question. At first I thought CopyMemory because memcpy appeared to be an export from crtdll.dll and msvcrt.dll - but after looking at kernel32.dll and ntdll.dll - I found the export for memcpy in ntdll.dll - so I would think memcpy would be faster. The reality probably has to do more with the compiler and where it links the code from.

shazbot

Edited by - daerid on March 4, 2002 4:59:16 PM

daerid - Look at the timestamps on your initial post and Lessbread''s. He didnt read yours before posting.

The computer was conceived as a tool to reduce complexity. Some people found this loss of complexity unacceptable, and developed UNIX to amend the situation.

Don''t you hate the "race conditions" in posting? That''s probably why they let you to delete posts.

quote:

---

Original post by Arild Fines
daerid - Look at the timestamps on your initial post and Lessbread''s. He didnt read yours before posting.

---

Yep. I didn''t see his first post until after I posted. Then I saw his second post with all those CAPITAL LETTERS and I thought he was just a spazz...

On x86 they''re the same, and they''re generally generated as intrinsics (i.e. inlined asm) rather than library calls.