| ??? 07/08/08 01:11 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#156501 - Or turn it down as needed Responding to: ???'s previous message |
Most of the time it is not the optimized code does not work and the unoptimized does. It is the optimized code can not be debugged.
So turn it down debug then turn it on. If the less optimized code is small and fast enough maybe leave it. Leaving it low then complaining C it to slow on a micro you have to do it in ASM can be the final result of that path. |
| Topic | Author | Date |
| Why Is Debugging Optimized Code Such an Issue? | 01/01/70 00:00 | |
| Usually not | 01/01/70 00:00 | |
| False Assumptions | 01/01/70 00:00 | |
| "language specification" ?? | 01/01/70 00:00 | |
| Do not assume it is that easy | 01/01/70 00:00 | |
| Common Stuff Leading To Errors | 01/01/70 00:00 | |
| "common stuff" falling apart when optimized | 01/01/70 00:00 | |
| How broken things work | 01/01/70 00:00 | |
| It is not like that | 01/01/70 00:00 | |
| A bad workman blames his tools | 01/01/70 00:00 | |
| A common side effect of optimisation | 01/01/70 00:00 | |
| Newbies | 01/01/70 00:00 | |
| another good reason | 01/01/70 00:00 | |
| a rule of thumb | 01/01/70 00:00 | |
| excellent advice, however - and | 01/01/70 00:00 | |
| Defeatist? | 01/01/70 00:00 | |
| Or turn it down as needed | 01/01/70 00:00 | |
| Using Pragmas During Debugging | 01/01/70 00:00 | |
| Free lunch? | 01/01/70 00:00 | |
| a dream | 01/01/70 00:00 | |
| If it were easy everone would be doing it. | 01/01/70 00:00 | |
you can't | 01/01/70 00:00 |