> Description:
> memcpy() can be optimized in wacky way by compilers (is NOT a normal function),
> and can raise alignment issues.
> Modified files:
> File: tcpdump/addrtoname.c; Revision: 1.77;
> Date: 2001/06/24 21:35:53; Author: itojun; Lines: (+7 -7)
"Wacky" seems to imply "buggy" here - if the implementation, say,
#defines "memcpy" as "__builtin_memcpy", and handles "__builtin_memcpy"
specially, I'd consider it broken if there are alignment issues if the
code doesn't undefine "memcpy" (so that "__builtin_memcpy" is used) that
don't occur if the code does undefine "memcpy" (so that the library
routine "memcpy" is called).
On what platforms (CPU/OS/compiler) do these alignment bugs occur?
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
