??? 03/04/09 08:46 Read: times |
#163055 - As flash gets bigger, the code steps do too. Responding to: ???'s previous message |
I would agree with you completely. If an high volume application has to use a 4k part instead of a 2k part. It is a struggle to use a HLL and squeeze the code.
As chip sizes increase, a 8k part jumping to a 16k part is significant but once done there is a very big jump to a 32k, 64k part ... However once the HLL "baggage" has been linked in, there is no extra size costs of calling a C library function a second time. So your time, maintainability, availability of chips etc all come into the equation. You will make your own decisions. I would argue that most compilers do a pretty good job for 8 bit operations. Pointer manipulation can possibly be hand-optimised for a critical area. But I suspect that most applications have very few critical areas. Richard's vast expertise is then trumped by some young whippersnapper optimising one or two functions. And most importantly the young whippersnapper's code is maintainable by even younger whippersnappers. The large ASM program will never be maintained by anyone other than Richard. David. |