Re: gcc - setting the uninitialized state (tainting variables)

Campbell Barton writes: > Hi, I was looking into the possibility of setting a variable as > uninitialized again (after its been initialized at least once > already). > > [...] > > Is this possible or has it been considered before? What languages are you targetting? In modern C and C++, I would

gcc-4.9-20130526 is now available

Snapshot gcc-4.9-20130526 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20130526/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.9 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk

gcc - setting the uninitialized state (tainting variables)

Hi, I was looking into the possibility of setting a variable as uninitialized again (after its been initialized at least once already). This could be handy for track simple errors when a variables been used after its value is logically invalid (where its initialized but the developer decides the v