This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.0.1 Status
- To: scott snyder <snyder at fnal dot gov>
- Subject: Re: GCC 3.0.1 Status
- From: Nathan Sidwell <nathan at codesourcery dot com>
- Date: Tue, 03 Jul 2001 20:40:12 +0100
- CC: gcc at gcc dot gnu dot org, Mark Mitchell <mark at codesourcery dot com>, jason at redhat dot com
- Organization: Codesourcery LLC
- References: <20620000.994106696@warlock.codesourcery.com> <yr84rstj0t4.fsf@d0sgibnl1.fnal.gov>
scott snyder wrote:
> My favorite 3.0 bug is the remaining virtual inheritance problem turned
> up by the test cases in c++/3145. This is a regression from 2.95 where
> we generate incorrect code; further, this shows up in building several
> relatively well-known packages (orbacus, aRts). As of now, this bug is
> not marked as high priority in GNATS. (It used to be, but was lowered
> to medium before the 3.0 release after a partial fix.)
Whilst 3145 was still failing, after fixing some ABI layout bugs, the
next bug appeared to be a long standing problem where gcc got confused
when there were multiple instances of the same non-virtual base type
within a virtual base. This did not appear to be a regression from
2.95 (though 2.95 might not have seg faulted, it would not have
produced correct layout). I did not investigate further.
Scott, if you've any particular test case which does not fall into
the above mentioned category, can you file it please? If you're not sure
whether your test case is one or the other, just file it. Although
3145 is great at stressing the algorithm, it is pants when it comes
to diagnosing a failure.
Jason, you put another patch to the vtt algorithm into the mainline
have/will you move it to the 3.0.1 branch?
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org