On Sat, 10 Sep 2016, Mark Kettenis wrote: > From: Philip Guenther <guent...@gmail.com> ... > > Also interesting that it generates memmove() calls. Wonder where it > > ended up doing that. > > Well, clang actually calls the functions with their standard name even > for the cases where we explicitly call those functions in the source > code. And since we do call memmove() in various places in the source > code, that's where they come from.
Ah. Still: it's totally ignoring our renaming for those? Thanks, clang! Guess I'll need to roll up my sleeves on this...
