From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii To: dberlin@redhat.com Cc: per@bothner.com, ac131313@cygnus.com, gdb@sources.redhat.com Subject: Re: C++ FAIL counts and the effect of demangler fix Date: Fri, 16 Feb 2001 02:32:00 -0000 Message-id: <200102161032.FAA04544@indy.delorie.com> References: <200102141649.IAA28922@bosch.cygnus.com> <3A8C1E5E.F4A2C5E2@cygnus.com> <200102160735.CAA01234@indy.delorie.com> X-SW-Source: 2001-02/msg00209.html > From: Daniel Berlin > Date: 16 Feb 2001 03:57:11 -0500 > > Eli Zaretskii writes: > > > > From: Per Bothner > > > Date: 15 Feb 2001 13:54:02 -0800 > > > > > > Andrew Cagney writes: > > > > > > > o I don't want GDB's release schedule in > > > > someway directly tided to GCC's release > > > > schedule. > > > > > > I think that is unavoidable, given that Gcc 3 has a new and > > > incompatible C++ ABI. It is Bad if the current release of Gdb cannot > > > debug code produced from the current release of Gcc. Therefore, Gdb > > > 5.1 should be released before or at the same time as Gcc 3.0 is > > > released, and it needs to have at least tolerable support for the new > > > C++ ABI. [snip] > > > > If there are important reasons why the next release of GDB should > > support the new C++ ABI, then perhaps the GCC team should help Daniel > > and others work on the GDB side of this support. [snip] > I don't agree with this. > The GCC team is responsible for GCC, not GDB. [Sorry for the long quotations, they are necessary in this case.] Let me back up for a moment. See the quotations above; it goes like this: - Andrew says he doesn't want GDB's release schedule to be directly tied to GCC's releases (FWIW, I'm with Andrew on this one); - Per replies that it is very important that GDB _does_ release its new version with the new C++ ABI support together with GCC 3.0; - To this I say that if the GCC teams wants it so badly, they should come on board and help. In other words, I also don't think that the GCC team should be developing GDB. What I am saying is that if they think our decisions are not good enough for them, they have the opportuninty to make a difference by contributing the code.