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: Christian Iseli <chris at lslsun dot epfl dot ch>
- Subject: Re: Live range splitting in new allocator
- From: Michael Meissner <meissner at cygnus dot com>
- Date: Wed, 31 Jan 2001 09:53:14 -0500
- Cc: jbuck at racerx dot synopsys dot com, Marc dot Espie at liafa dot jussieu dot fr, aoliva at redhat dot com, espie at quatramaran dot ens dot fr, dewar at gnat dot com, gcc at gcc dot gnu dot org
- References: <200101310833.JAA10213@lslsun.epfl.ch>
On Wed, Jan 31, 2001 at 09:33:34AM +0100, Christian Iseli wrote:
> > 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
Ummm, -finitialize-stack[=value] would seem to make more sense than
initialize-all, since you would not be initializing the statics or globals (or
possibly the registers).
> 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
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: meissner@redhat.com phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482