| ??? 04/16/08 19:10 Read: times |
#153557 - The problem is obvious ... Responding to: ???'s previous message |
You shouldn't use 'C' or C++ until you're totally competent in using ASM. Once you know exactly how to write the entire code set in ASM, you can enhance maintainability by writing it in 'C' or whatever.
HLL's are OK for machines with GB of memory and PB of external storage, with GIPS of performance, though the HLL's are nearly always a guarantee of introduced bugs and inefficiencies. If you have a task of 1E6 lines or more, well, maybe then an HLL might be worth a look, but a good macro-assembler is always safer. With an HLL compiler you're just introducing another level of uncertainty. Once you attain enough familiarity with the MCU and the compiler to reduce the uncertainty, you know enough to write the ASM better than the compiler can. RE |
| Topic | Author | Date |
| SDCC XRAM Problem | 01/01/70 00:00 | |
| Sounds like ... | 01/01/70 00:00 | |
| I *think* I have that covered... | 01/01/70 00:00 | |
| it is NOT | 01/01/70 00:00 | |
| Assembly | 01/01/70 00:00 | |
| I'll try anything once | 01/01/70 00:00 | |
| OK, here is a way | 01/01/70 00:00 | |
| ANSI C | 01/01/70 00:00 | |
| SDCC startup | 01/01/70 00:00 | |
| unsigned char _sdcc_external_startup(void) | 01/01/70 00:00 | |
| holy cow | 01/01/70 00:00 | |
| The problem is obvious ... | 01/01/70 00:00 | |
| I'm not that bombastic, but agree in principle wit | 01/01/70 00:00 | |
| When someone is familiar with it as you are ... | 01/01/70 00:00 | |
| show me one from this year | 01/01/70 00:00 | |
| You have taken my comment wrong. | 01/01/70 00:00 | |
| My Guess Is That... | 01/01/70 00:00 | |
not always ... | 01/01/70 00:00 | |
| obscure? | 01/01/70 00:00 |