This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PR c++/5645 gcc warns that pure virtual class not explicitly initialized

From: Jason Merrill <jason at redhat dot com>
To: Manuel López-Ibáñez <lopezibanez at gmail dot com>
Cc: Mark Mitchell <mark at codesourcery dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Nathan Sidwell <nathan at codesourcery dot com>
Date: Tue, 13 Nov 2007 12:18:30 -0500
Subject: Re: PR c++/5645 gcc warns that pure virtual class not explicitly initialized
References: <6c33472e0710271010s2a6cc785w1524bbf39b9f607a@mail.gmail.com> <472E58AD.6040001@codesourcery.com> <6c33472e0711111603i33c203afx930e2eb3bd8c1be2@mail.gmail.com> <4738C0DA.80903@redhat.com> <6c33472e0711121627v3946f828s6c6bb9b1d25de6ef@mail.gmail.com>

Manuel López-Ibáñez wrote:

TYPE_HAS_CONSTRUCTOR (BINFO_TYPE (subobject)) is 1.

That seems wrong to me. That's being set in add_implicitly_declared_members, but I don't see why; the macro is supposed to indicate whether or not there are any user-declared constructors. What happens if you remove the line that sets it for the implicit copy ctor?

Jason

Follow-Ups:
- Re: PR c++/5645 gcc warns that pure virtual class not explicitly initialized
  - From: Manuel López-Ibáñez

References:
- Re: PR c++/5645 gcc warns that pure virtual class not explicitly initialized
  - From: Mark Mitchell
- Re: PR c++/5645 gcc warns that pure virtual class not explicitly initialized
  - From: Manuel López-Ibáñez
- Re: PR c++/5645 gcc warns that pure virtual class not explicitly initialized
  - From: Jason Merrill
- Re: PR c++/5645 gcc warns that pure virtual class not explicitly initialized
  - From: Manuel López-Ibáñez

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]