This is the mail archive of the
mailing list for the GCC project.
Re: [patch c++]: Fix possible uninitialized variable
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Paolo Carlini <paolo dot carlini at oracle dot com>
- Cc: Kai Tietz <ktietz70 at googlemail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Jason Merrill <jason at redhat dot com>
- Date: Wed, 14 Jul 2010 13:58:33 +0200
- Subject: Re: [patch c++]: Fix possible uninitialized variable
- References: <AANLkTimEXaWjIOlkUzkeSq_Knr_uSM0P1cn_h9qCknffirstname.lastname@example.org> <4C3DA4F4.email@example.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Wed, Jul 14, 2010 at 01:52:20PM +0200, Paolo Carlini wrote:
> On 07/14/2010 12:26 PM, Kai Tietz wrote:
> > 2010-07-14 Kai Tietz
> > * method.c (synthesized_method_walk): Initialize
> > check_vdtor by false.
> > Tested for i686-pc-linux-gnu, i686-pc-mingw32, and x86_64-pc-mingw32.
> > Ok for apply?
> Frankly, I do not understand why you are proposing this change: at line
> 1007 check_vdtor is assigned false and there are no uses whatsoever
> before. Everything seems fine, and, by the way, the case of assign_p is
> quite similar. Are you seeing spurious warnings during the bootstrap?
That's because Jason fixed this yesterday:
Before that it has been really uninitialized.