Live range splitting in new allocator
Michael Meissner
meissner@cygnus.com
Wed Jan 31 06:53:00 GMT 2001
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
More information about the Gcc
mailing list