This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Patch to allow strlen expander to fail
- To: law at cygnus dot com
- Subject: Re: Patch to allow strlen expander to fail
- From: Joe Buck <jbuck at racerx dot synopsys dot com>
- Date: Mon, 6 Mar 2000 19:10:20 -0800 (PST)
- Cc: vonbrand at sleipnir dot valparaiso dot cl (Horst von Brand), gcc at gcc dot gnu dot org
> 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?