During simplification, a library function with an implementation body would mean that it is not a standard library call and hence simplification should be avoided.
This fixes code generation for bcopy when built with -D_FORTIFY_SOURCE since the simplification would otherwise transform the bcopy calls to memmove and not builtin_memmove_chk as is expected with source fortification.
And if it happens to be in another TU?