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 [thread overview]
Message-ID: <200105012021.QAA29190@makai.watson.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105011556270.29010-100000@www.cgsoftware.com>
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
next prev parent reply other threads:[~2001-05-01 13:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF70310855.A41D4A39-ON86256A39.00616113@i2.com>
2001-05-01 10:13 ` David Edelsohn
2001-05-01 13:02 ` Daniel Berlin
2001-05-01 13:22 ` David Edelsohn [this message]
2001-05-01 15:40 ` Kevin Buettner
2001-05-01 15:44 ` David Edelsohn
2001-05-01 16:21 ` Kevin Buettner
2001-05-01 19:15 ` David Edelsohn
[not found] <200104302116.RAA23290@makai.watson.ibm.com>
2001-05-02 23:25 ` Zack Weinberg
2001-05-03 1:42 ` Kevin Buettner
2001-05-15 15:27 ` Elena Zannoni
2001-05-15 15:31 ` David Edelsohn
2001-05-15 16:19 ` Elena Zannoni
2001-05-16 10:46 ` David Edelsohn
2001-05-16 11:15 ` David Edelsohn
2001-05-16 12:24 ` Elena Zannoni
[not found] <15106.54023.177141.275660@kwikemart.cygnus.com>
2001-05-16 12:37 ` David Edelsohn
2001-05-16 13:07 ` David Edelsohn
2001-05-16 13:51 ` Kevin Buettner
2001-05-16 14:06 ` Stan Shebs
2001-05-16 14:10 ` David Edelsohn
2001-05-16 14:32 ` Elena Zannoni
2001-05-16 21:29 ` Elena Zannoni
2001-05-17 15:27 ` David Edelsohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200105012021.QAA29190@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=dan@www.cgsoftware.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=nsd@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox