| ??? 07/06/08 19:01 Read: times |
#156437 - "language specification" ?? Responding to: ???'s previous message |
Yes, if the persons coding, and reviewing, are not familiar with dark corners of the language specification, that can happen.
I have yet to see the first timing bug resulting from someone "not familiar with dark corners of the language specification". Any bug that show up both optimized and non-optimized can be debugged by "standard means" in its non-optimised form. Erik |
| 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 |