| ??? 07/05/08 07:22 Read: times |
#156408 - A bad workman blames his tools Responding to: ???'s previous message |
Neil Kurzman said:
code that does not work when it is optimized may still be the coders fault. In fact, I would say that it is usually still the coder's fault! Just because the code works that does not mean it is correct and bug free. Absolutely! That means optimizing, adding code or variables, anything may make it fail. Probably the classic example in embedded applications is where the timing of the original code is marginal; so doing anything to it - including optimising - is likely to "break" it. The problem is that the original code was faulty - the optimisation has just brought that fault to light! newbies are very quick to blame the compiler. Very true! |
| 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 |