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: jbuck at racerx dot synopsys dot com, Marc dot Espie at liafa dot jussieu dot fr
- Subject: Re: Live range splitting in new allocator
- From: Christian Iseli <chris at lslsun dot epfl dot ch>
- Date: Wed, 31 Jan 2001 09:33:34 +0100 (MET)
- Cc: aoliva at redhat dot com, espie at quatramaran dot ens dot fr, dewar at gnat dot com, gcc at gcc dot gnu dot org
> Well, it would be better than what currently exists... as far as I knowm
> uninitialized locals tend to have value zero with -O0, which curiously enough,
> tends to hide many more bugs than any possible other choice...
Just a thought, but if someone goes to the trouble of implementing some automatic initialization,
it might be good to have a flag that says something like -finitialize-all=<some value>
Then you test your code using
-finitialize-all=0
-finitialize-all=0xdeadbeef
-finitialize-all=random
Could maybe even be setup at runtime, to avoid the recompile, and depend on some environment
variable:
-finitialize-all=envvar
ALL_INIT=1012 mytestprogram
Cheers,
Christian