From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Edelsohn <dje@watson.ibm.com>
To: Daniel Berlin <dan@www.cgsoftware.com>
Cc: Nicholas Duffek <nsd@redhat.com>, Kevin Buettner <kevinb@redhat.com>, gdb@sources.redhat.com
Subject: Re: Limited success with 3.0 branch on AIX 
Date: Tue, 01 May 2001 13:22:00 -0000
Message-id: <200105012021.QAA29190@makai.watson.ibm.com>
References: <Pine.LNX.4.33.0105011556270.29010-100000@www.cgsoftware.com>
X-SW-Source: 2001-05/msg00020.html

	The AIX stab-like choices are:

#define C_GSYM          0x80
#define C_LSYM          0x81
#define C_PSYM          0x82
#define C_RSYM          0x83
#define C_RPSYM         0x84
#define C_STSYM         0x85
#define C_TCSYM         0x86
#define C_BCOMM         0x87
#define C_ECOML         0x88
#define C_ECOMM         0x89
#define C_DECL          0x8c
#define C_ENTRY         0x8d
#define C_FUN           0x8e
#define C_BSTAT         0x8f
#define C_ESTAT         0x90

	C_GSYM seemed to make the most sense to me.  Would gdb looking in
N_GSYM cause a problem for any other ports?  Should gdb look there only
for AIX?

	Would N_GSYM symbol cause a conflict if a programmer really chose
to declare a global symbol named "gcc2_compiled."?  Given the definition
of N_GSYM, it seems that this only would define a duplicate stabs entry
and not conflict with a real symbol of that same name because the stabs
value is ignored.

	I would like to get a patch into GCC ASAP, but I want it to match
what GDB expects / can handle.  So I would like to get a decision to use
G_NSYM or an alternate AIX stabs type, and get the simple changes into GCC
and GDB.

Thanks, David