| ??? 09/25/06 19:21 Read: times |
#125036 - Thats not the point Responding to: ???'s previous message |
All I was trying to say was beware of things like the compiler desiding to defer popping the stack untill a few function calls after it strictly needs to and or reordering or even reversing loop counters,re-ordering memory accesses and optimising away variables.
Its not about timings as such,certainly with gcc for the avr its quite possible for the compiler to produce 50% bigger code when all the optimisations are turned on and its not easy to see where the compiler has desided to delay a branch ofr example and if you are expecting to be able to alter a variable in a simulator then there are going to be side effects in that kind of situation. |
| Topic | Author | Date |
| debuging C code | 01/01/70 00:00 | |
| Management solution | 01/01/70 00:00 | |
| I kind of hope | 01/01/70 00:00 | |
| False assumption | 01/01/70 00:00 | |
| to HLL or not to HLL | 01/01/70 00:00 | |
| Things for which an HLL cannot be trusted... | 01/01/70 00:00 | |
| sometimes there's no other way | 01/01/70 00:00 | |
| that was not me, but Andy | 01/01/70 00:00 | |
| Timing - end of wrong stick | 01/01/70 00:00 | |
| Thats not the point | 01/01/70 00:00 | |
| better, don't use C at all.. :-) | 01/01/70 00:00 | |
| experience and knowledge | 01/01/70 00:00 | |
| the key word is "manifest" | 01/01/70 00:00 | |
| NASA | 01/01/70 00:00 | |
| against NASA rules, sorry Andy posted before | 01/01/70 00:00 | |
| Testing | 01/01/70 00:00 | |
| Pointers | 01/01/70 00:00 | |
| In the real world | 01/01/70 00:00 | |
| worse than that | 01/01/70 00:00 | |
customers complaining or not ... | 01/01/70 00:00 |