This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Your recent change
- To: mark at codesourcery dot com
- Subject: Re: Your recent change
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Sun, 26 Mar 00 13:12:54 EST
- Cc: gcc-bugs at gcc dot gnu dot org
I plan on mandating that no tests should have unexpected failures,
except when they have just broken. That will make it easy for people
to know what's a failure and what's not.
Yup. But we know there are problems on in tree.
There are different values in the vtables, indicating that somehow
base classes are ending up at different offsets in their parents.
I'm so ignorant of C++ that I'm not even totally sure what a "base class" is.
Clearly this is due to some of the BINFO stuff being wrong, but a little
more direction would help me *a lot*. Thanks!