Using C in Embedded systems is a great convenience, but one needs to be careful to know when a piece of code is compiler dependent. Often one writes compiler dependent code unknowingly in an embedded system where our abstraction of hardware is quite less, and havoc is just around the corner. This paper provides guidelines, thumb rules, and a checklist of what has to observed to write embedded code that does not run into trouble on any C compiler.