On Tue, Jan 19, 2021 at 9:04 PM unlvsur unlvsur via Gcc <gcc@gcc.gnu.org> wrote: > > That is not for inline. That is to allow implementing memcpy without > introducing any libc runtime which allows us to use it in freestanding > environment.
Note that GCC requires memcpy, memmove, memset and memcmp to exist even in a freestanding environment since it may generate calls to those functions itself. So the argument of a freestanding env does not hold. Richard. > Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 > > From: Segher Boessenkool<mailto:seg...@kernel.crashing.org> > Sent: Tuesday, January 19, 2021 13:52 > To: unlvsur unlvsur<mailto:unlv...@live.com> > Cc: gcc@gcc.gnu.org<mailto:gcc@gcc.gnu.org>; > gcc-h...@gcc.gnu.org<mailto:gcc-h...@gcc.gnu.org> > Subject: Re: Should GCC provide __builtin_memcpy_inline like clang does? > > On Tue, Jan 19, 2021 at 11:33:56AM +0000, unlvsur unlvsur via Gcc-help wrote: > > I think __builtin_memmove_inline, __builtin_memset_inline can also get > > provided. > > > > That allows better performance for small size copies > > You normally will get better performance by letting the compiler figure > out whether to inline or not. That is what the Power port does, for > example. > > > and allowing memcpy to be usable without libc. > > You can provide your own non-standard-named function anyway? > > > In either case, feature requests should go into bugzilla, or they will > more than likely be lost. > > Thanks, > > > Segher >
