From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Edelsohn <dje@watson.ibm.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: Kevin Buettner <kevinb@cygnus.com>, "Zack Weinberg" <zackw@Stanford.EDU>, Matthew Conway <matt_conway@i2.com>, Mark Mitchell <mark@codesourcery.com>, gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Limited success with 3.0 branch on AIX 
Date: Wed, 16 May 2001 13:07:00 -0000
Message-id: <200105162006.QAA25648@makai.watson.ibm.com>
References: <15106.54023.177141.275660@kwikemart.cygnus.com>
X-SW-Source: 2001-05/msg00280.html

	First, I agree that the XFT_CV field of the File Auxilliary Entry
for C_FILE Symbols is the optimal location for this type of GCC DBX
Marker.  We just do not have a way of accessing that field with the
current tools.

	What exactly is the "gcc2_compiled." symbol used to enable in GDB?
How much will it hurt if GDB debugs a GCC-compiled application and does
not know it was compiled with GCC?

	We seem to have the following options:

1) Do not include "gcc2_compiled." symbol in AIX XCOFF files until
   assembler provides feature to access XFT_CV field.
2) Always use compatible assembler feature available now, e.g. C_GSYM.
3) Use XFT_CV field if assembler supports the feature, otherwise fallback
   to C_GSYM.  Have GDB look in both locations, in addition to historical
   "gcc2_compiled." label.

David