If the compiler's output meets your performance requirements, and if it fits the code space within your system, there is absolutely no reason why you shouldn't use 'C' or Pascal. However, if there's a conflict, either with performance requirements or with code space, then a competent and responsible programmer would look at the ASM output from his compiler and see whether there isn't some reduction in either size or time lost, that can be gained by rewriting parts of the code in ASM before complaining that the available resources are either too small or too slow.

It's conceivable, of course, that the chosen MCU could be too slow or that the MCU code space, or available data space, is too small. Unless the programmer is the one who specified it, it's not a sin to make that claim. Increasing the per-product cost because he's unwilling to write in ASM is a mistake ... one that could get the programmer fired, and blackballed. A few 8-day weeks of 30-hour days rewriting his bloated 'C' code in ASM will teach him about using macros and subroutines. That'll make it fit.

RE