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] |
Hi, 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 ;) decision?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 ;)
Thanks! Paolo.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |