This is the mail archive of the
mailing list for the GCC project.
Re: [C++ patch] Move FINAL flag to middle-end trees.
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Jan Hubicka <hubicka at ucw dot cz>
- Cc: Jason Merrill <jason at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Thu, 22 Aug 2013 18:05:05 +0200
- Subject: Re: [C++ patch] Move FINAL flag to middle-end trees.
- References: <20130822095937 dot GF16124 at kam dot mff dot cuni dot cz> <52162B9B dot 5060905 at redhat dot com> <20130822152254 dot GC19256 at kam dot mff dot cuni dot cz>
On 08/22/2013 05:22 PM, Jan Hubicka wrote:
Sorry if I'm saying something rather vague: I suppose you mean
BINFO_FLAG_6? Because it's the last one. I'm saying this because over
the last week or so I wondered if we need a bit also to fix c++/15272.
Can we give that a little thought before making the final (pun intended
On 08/22/2013 05:59 AM, Jan Hubicka wrote:
+/* Nonzero if RECORD_TYPE represents a final derivation of class. */
+#define TYPE_FINAL_P(NODE) \
+ (RECORD_OR_UNION_CHECK (NODE)->base.default_def_flag)
How about if we put this flag on the BINFO rather than the type itself?
No problem for me. There is space in type flags and binfo flags, so whatever
seems more suitable.
This option did not occured to me and of course I would be bit fearing of C++ FE
not having binfos ready all the time it wants to touch the type. But probably
you know if that can happen ;)