This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH]: Track uninitialized variables



On May 9, 2007, at 9:48 AM, Caroline Tice wrote:



As I mentioned, this is mostly for help with debugging optimized code. Sometimes bugs that seem to "magically appear" when optimizations get turned on are actually caused by uninitialized variables having a different value when the optimizations change the data layout. In the unoptimized version the value happened to be benign, but in the optimized version the value causes bad things to happen. Therefore it would help programmers quite a bit, when attempting to debug their optimized code, if the debugger could point out when a variable did not get optimized.
^^^^^^^^^^^^^^^^
Typo: That was supposed to say, "when a variable did not
get initialized".



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]