Patch to allow strlen expander to fail

[Joe Buck]

> Any code which depends on gcc generating or not generating libcalls is
> broken.

Let a and b be of type "struct foo".

Then it would appear that the statement

	a = b;

is broken.  How should this code be fixed?

>   > There was recently a problem with the Linux kernel because gcc
>   > willy-nilly called memcpy(3), and that one isn't around in the kernel,
> Then that's a kernel problem.  They're depending on a specific, undocumented
> and highly implementation dependent behavior in the compiler.  That's dumb.

Again, what's the fix?  Should the Linux kernel's inline memory copy
routine be named memcpy?