ad284e38a3
and as long as we're not compiling with IPA, gcc(1) won't optimize the call away. The whole purpose of using memcpy(3) is to avoid misaligned loads and stores when we need to read or write the value in the unaligned memory location. But if gcc(1) optimizes the call to memcpy(3) away, it will typically introduce misaligned loads and stores. In this context that's not a good idea. |
||
---|---|---|
.. | ||
build | ||
debugscripts | ||
diag | ||
kerneldoc | ||
KSE | ||
lib32 | ||
LibraryReport | ||
regression | ||
sched | ||
test | ||
tools | ||
install.sh | ||
make_libdeps.sh | ||
README |
$FreeBSD$ This directory tree contains tools used for the maintenance and testing of FreeBSD. There is no toplevel Makefile structure since these tools are not meant to be built as part of the standard system, though there may be individual Makefiles in some of the subdirs. Please read the README files in the subdirs for further information.