This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch for C++ uninitialized pointer-to-member value
On May 13, 2002, Jason Merrill <jason@redhat.com> wrote:
>> Ok. I didn't find a nice way to merge the code from
>> build_default_init into it, thought. Is this ok?
> Much of build_default_init can be moved to build_forced_zero_init and
> replaced with a call; only the NEEDS_CONSTRUCTING and reference cases need
> to be retained.
Yeah, but then I'd have to remove the sanity check from
build_forced_zero_init(), that is supposed to catch types that don't
really need forced zero initialization. Besides,
build_forced_zero_init() does not handle ENUMERAL_TYPEs, so it would
call digest_init() an initializer of the wrong type, unless I moved
this handling into forced_zero_init().
Is this what you have in mind?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer