Re: [PATCH] C undefined behavior fix

Alan Cox
2002-01-03T00:17:25Z

> Yes, but doesn't -ffreestanding imply that gcc _can't_ assume this is
> the standard library, and that strcpy _might_ not be what it thinks, and
> to just call strpy?

strcpy is part of the C standard. You'd need a -fits-not-c-its-linux

> We aren't saying this is always a bad thing, but what if we want to turn
> off a built-in optimization? Unless -ffreestanding stops implying
> -fno-builtin (maybe we could just add -fno-builtin for this one file..),
> this line should be fine.

If you want a strcpy that isnt strcpy then change its name or use a
different language 8)