Timeline for Is it really a good-practice disable optimizations during the development and debugging phases?
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2011 at 17:43 | comment | added | Kortuk | @OEngenheiro, Take a look at some of the books Jack Ganslle recommends if you want applied to embedded systems. Otherwise I would assume asking SO would be a great way to get the CS books on this practice. | |
| Mar 20, 2011 at 17:39 | comment | added | Kortuk | @Reemrevnivek, I would disable single file optimizations which has effect and overall timing but then use the file to benchmark and test other systems. With all optimizations I would use LED blinking and such measured with an oscope to measure timings. | |
| Aug 6, 2010 at 20:44 | comment | added | Kevin Vermeer | Again, not for the C30 compiler, but gcc publishes a LONG list of the various optimizations which can be applied. You can also use this list to get fine-grained optimization, in case you have a particular control structure you want to keep intact. The list is here: gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html | |
| Aug 6, 2010 at 20:43 | comment | added | Michael Kohne | @O Engenheiro: Check your compiler docs for what optimizations it supports. Optimization varies wildly depending on compiler, libraries, and target architecture. | |
| Aug 6, 2010 at 19:30 | comment | added | Mark | I haven't worked with the C30 compiler but for the C18 compiler there was an app note/manual for the compiler that covered what optimizations it supported. | |
| Aug 6, 2010 at 19:17 | comment | added | Daniel Grillo | Where can I learn more about this? | |
| Aug 6, 2010 at 19:14 | comment | added | Kevin Vermeer | The counterpoint to this argument is that the optimizer likely will make things smaller and/or faster, and if you've got timing or size constrained code then you may break something by disabling the optimization, and waste your time debugging a problem that doesn't really exist. Of course, the debugger may make your code slower and larger as well. | |
| Aug 6, 2010 at 19:10 | history | answered | Michael Kohne | CC BY-SA 2.5 |