??? 07/11/08 12:55 Modified: 07/11/08 12:58 Read: times |
#156608 - different approaches Responding to: ???'s previous message |
Use IAR then
IAR makes a "general compiler" for all the families they support and this "C body" one optimizes heavily (volume sold). Then, because of the "generality" some things that is optimal under the '51 architecture, but not in a general sense get lost, so in case a) they are somewhat optimal, in case b) they are not. Keil makes a dedicated '51 compiler and thus the "C body" is not the same volume as IAR, the result is that in case a) they are not optimal, in case b) they are somewhat optimal. My impression (I have not analyzed this to death) is that non-optimized Keil is the most efficient and, if you want the debugging nightmare of running optimized code you may be better off with IAR. Now, one argument for Keil is that most '51 ISP/JTAG etch providers work in conjunction with Keil. Erik |
Topic | Author | Date |
Data Array getting corrupted after init | 01/01/70 00:00 | |
OnePossibleIdea.... | 01/01/70 00:00 | |
I did not do anything with the stack | 01/01/70 00:00 | |
As Michael said.... | 01/01/70 00:00 | |
How do you test and debug code? | 01/01/70 00:00 | |
Keil is the only thing in place | 01/01/70 00:00 | |
'crap'?? | 01/01/70 00:00 | |
Is this the book you refer? | 01/01/70 00:00 | |
nope | 01/01/70 00:00 | |
Erik | 01/01/70 00:00 | |
So where is the code | 01/01/70 00:00 | |
do NOT "put them" | 01/01/70 00:00 | |
Focus | 01/01/70 00:00 | |
Simulator | 01/01/70 00:00 | |
So this is on a simulator? | 01/01/70 00:00 | |
Post your duff code | 01/01/70 00:00 | |
Finding Cause of Corruption | 01/01/70 00:00 | |
Get the C right, then look at the target CPU | 01/01/70 00:00 | |
Optimizing Compilers | 01/01/70 00:00 | |
In my experience..... | 01/01/70 00:00 | |
Keil C 51 Optimizations | 01/01/70 00:00 | |
Use IAR then | 01/01/70 00:00 | |
different approaches | 01/01/70 00:00 | |
sometimes, depends | 01/01/70 00:00 | |
Thanks![]() | 01/01/70 00:00 |