6
I am studying the architecture and implementation in MIPS, but as I do not work at low level what I am doing are basic initial exercises in any beginning of learning, I would like to know what are the real difficulties and problems of a developer in Assembly?!
For example for the development of embedded systems.
5
The main problems are:
1) The work yields very little, because each Assembly instruction does very little.
2) Control structures are scarce, you basically have "Jump" and nothing else.
3) The developer will need to decorate a compendium of instructions that only applies to a processor, sometimes apply only to a range of models, so it’s a knowledge that gets obsolete fast.
4) Portability is compromised; copying code from another project involving another architecture is complicated.
5) In theory a program written in Assembly is faster than any other, but this can no longer be true with new models of processors, in which your program still works but the instructions no longer work in the same way as before; who writes compilers know this long before the processor comes on the market.
Using Assembler still makes sense to access special instructions, which compilers do not take advantage of. This is the case of some mathematical optimizations, DSP controllers, hardware accelerated encryption, etc.
Browser other questions tagged software-architecture assembly architecture-computers mips
You are not signed in. Login or sign up in order to post.