| ??? 06/22/07 12:34 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#141156 - Fly what you TEST; TEST what you fly Responding to: ???'s previous message |
There is a difference between debugging and testing. Debugging is what you do when your testing exposes a fault, so that you can find and fix it.
So, you can run through your tests with optimization enabled and everything as you'd expect for your finally ship. If a test fails, use your box of debugging tools to find out what went wrong, possibly tracing your code (where optimization has to be turned), fix the problem and test your optimized code ad nauseam, until you're happy everything works. If you can fit unoptimized code in your end device, and you're happy with the performance of that code, by all means test and debug with that. In an embedded context however, that is not always practical. |
| Topic | Author | Date |
| stepping throught "c" code | 01/01/70 00:00 | |
| Optimizations. | 01/01/70 00:00 | |
| Optimization Level ? | 01/01/70 00:00 | |
| Yep, very likely the optimization | 01/01/70 00:00 | |
| Fly what you debug; Debug what you fly | 01/01/70 00:00 | |
| Fly what you TEST; TEST what you fly | 01/01/70 00:00 | |
| It's about time | 01/01/70 00:00 | |
| OH? | 01/01/70 00:00 | |
| Re: OH? | 01/01/70 00:00 | |
| If you have a very complicated calculation | 01/01/70 00:00 | |
| break it up | 01/01/70 00:00 | |
| I give up | 01/01/70 00:00 | |
Nevermind | 01/01/70 00:00 | |
| Debugging problems | 01/01/70 00:00 | |
| Update | 01/01/70 00:00 |