This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Live range splitting in new allocator
- To: espie at quatramaran dot ens dot fr, jbuck at racerx dot synopsys dot com
- Subject: Re: Live range splitting in new allocator
- From: dewar at gnat dot com
- Date: Tue, 30 Jan 2001 12:41:09 -0500 (EST)
- Cc: dewar at gnat dot com, gcc at gcc dot gnu dot org
<<For floating point on IEEE platforms, it's easy enough: use a NaN.
However, for variables that are used as boolean values (whether a C++ bool
or a C int used as a flag), you'll make things more deterministic than
before: an uninitialized Boolean auto variable used to be random, under your
proposal it will always be true.
If you want to go down this road, you could go all the way and generate
code that catches all uses of uninitialized variables.
>>
Don't let best be the enemy of good! Catching all uses of uninitialized
variables is very hard, and requires modification of data structures
that may disturb bug finding as well.
It is actually a good thing to make things more deterministic when debugging
for most purposes.