| ??? 07/07/08 05:35 Read: times |
#156452 - Common Stuff Leading To Errors Responding to: ???'s previous message |
Neil Kurzman said:
The common stuff is just as bad as the dark corners. It is why the users of "real HLL" complain about C. uninitialized variables and pointers. Off by one errors in arrays. Pointers to the wrong memory. Would these errors show up only in the optimized code and not in the non-optimal code? Would be grateful for some examples. Neil Kurzman said:
Embedded systems add another layer of pit falls. Interrupts, Atomic operations, and the details of the hardware. Agreed. No fault of the optimizer. |
| 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 |