> > I *think* this isn't a problem for CONFIG_FORTIFY, since these will be > replaced and checked separately -- but it still seems strange that you > need to explicitly use __builtin_memcpy. > > Does this end up changing fortify coverage? Is fortify relevant here? Note that the whole file is compiled with __NO_FORTIFY.
