Messages in this thread | | | Subject | Re: [PATCH] C undefined behavior fix | From | Momchil Velikov <> | Date | 03 Jan 2002 18:48:56 +0200 |
| |
>>>>> "Edgar" == Edgar Toernig <froese@gmx.de> writes:
Edgar> David Woodhouse wrote: >> >> What part of 'undefined behaviour' is so difficult for people to understand?
Edgar> The behaviour is undefined by the C standard. But the mentioned Edgar> pointer arithmetic is defined in the environment where it has been Edgar> used. GCC tries to optimize undefined C-standard behaviour. And Edgar> IMHO that's the point. It may optimize defined behaviour and should Edgar> not touch things undefined by the standard.
How do you imagine that "not touch" ? like "#if 0 ... #endif" ?
Edgar> PS: Hey, we are talking about C, the de luxe assembler! *g*
Standard is a standard. Broken code is broken code. Sometimes you can get away with it, sometimes you can't and when you can't you fix the code. Or define your own standard and make a compiler implementing it.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |