Date: Fri, 27 Feb 2009 14:12:21 +0100 From: Roman Divacky <rdivacky@freebsd.org> To: Ed Schouten <ed@80386.nl> Cc: FreeBSD Arch <freebsd-arch@freebsd.org> Subject: Re: Making LLVM happy: memmove() in the kernel Message-ID: <20090227131221.GA60215@freebsd.org> In-Reply-To: <20090227131155.GE19161@hoeg.nl> References: <20090227131155.GE19161@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 27, 2009 at 02:11:55PM +0100, Ed Schouten wrote: > Hi all, >=20 > The FreeBSD+LLVM folks* noticed Clang generates calls to memmove() by > itself. I have yet to confirm this, but I assume this is done when > performing copies of structs greater than a certain size. In our kernel, > we don't have a memmove() function, but we do have a bcopy(). also.. quoting from (http://gcc.gnu.org/onlinedocs/gcc-4.2.1/gcc/Standards.html):=20 Most of the compiler support routines used by GCC are present in libgcc, but there are a few exceptions. GCC requires the freestanding environment provide memcpy, memmove, memset and memcmp. we were just lucky to not run into this --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmn5rQACgkQLVEj6D3CBEztSwCfVjrriHHKEHgaKppLUzdU7uiB LxMAnipEEOvoxdZvhJsOFiSlCg8jg0UW =HfWo -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090227131221.GA60215>