This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Helping out GDB
- To: dberlin at redhat dot com, dje at watson dot ibm dot com
- Subject: Re: Helping out GDB
- From: "James L. Dein" <jdein at windriver dot com>
- Date: Fri, 14 Jul 2000 10:35:21 -0700 (PDT)
- Cc: gcc at gcc dot gnu dot org
> From gcc-return-18847-jdein=wrs.com@gcc.gnu.org Wed Jul 12 12:37 PDT 2000
> Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
> List-Unsubscribe: <mailto:gcc-unsubscribe-jdein=wrs.com@gcc.gnu.org>
> List-Archive: <http://gcc.gnu.org/ml/gcc/>
> List-Post: <mailto:gcc@gcc.gnu.org>
> List-Help: <http://egcs.cygnus.com/ml/>
> Delivered-To: mailing list gcc@gcc.gnu.org
> To: dberlin@redhat.com
> cc: gcc@gcc.gnu.org
> Subject: Re: Helping out GDB
> Date: Wed, 12 Jul 2000 15:35:37 -0400
> From: David Edelsohn <dje@watson.ibm.com>
>
> The version of GCC implementing the new ABI is going to be
> gcc-3.0. I would expect that the symbol "gcc2_compiled." should be
> changed to "gcc3_compiled." Do any applications rely upon the symbol
> "gcc2_compiled." other than GDB? GDB could detect "gcc3_compiled." to
> flag the current use of "gcc2_compiled." and the new C++ ABI.
VxWorks requires 'gcc2_compiled.'. When gcc3_compiled. comes out, it will need
that too.
Jim Dein
>
> Let me guess: We are going to need to emit both "gcc2_compiled."
> and "gcc3_compiled." for backwards compatibility with GDB instead of
> updating the symbol atomically. At least that gives us another "bit" when
> "gcc3_compiled." symbols exists and "gcc2_compiled." symbol eventually is
> removed (:^).
>
> David