From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com
Subject: Namespaces with gcc v3 stabs+?
Date: Thu, 05 Dec 2002 16:31:00 -0000 [thread overview]
Message-ID: <200212060031.gB60Vt517871@duracef.shout.net> (raw)
Question for Daniel J or David C or Kevin B or anybody who knows
about v3 and stabs support ...
I'm looking at disimprovements from gcc v2 to gcc v3. One of the
issues is that gcc 2.95.3 / stabs+ emits stab information
for symbols in namespaces, but gcc 3.2.1 / stabs+ emits the stab
information with the wrong name.
Here is a test program:
namespace AAA
{
char mychar;
}
Here is the output with gcc 2.95.3:
# gcc 2.95.3, -gstabs+, native i686-pc-linux-gnu
.stabs "_3AAA.mychar:G(0,2)",32,0,3,0
.globl _3AAA.mychar
.bss
.type _3AAA.mychar,@object
.size _3AAA.mychar,1
_3AAA.mychar:
.zero 1
And here is the output with gcc 3.2.1:
# gcc 3.2.1, -gstabs+, native i686-pc-linux-gnu
.globl _ZN3AAA6mycharE
.bss
.type _ZN3AAA6mycharE,@object
.size _ZN3AAA6mycharE,1
_ZN3AAA6mycharE:
.zero 1
.stabs "mychar:G(0,2)",32,0,3,0
Notice how the stab refers to "mychar", not "_ZN3AAA6mycharE".
The output is similar with gcc 3.0.4, gcc 3.1, gcc 3.1.1, gcc 3.2,
and gcc HEAD%20021203.
Is this ringing any bells?
Kevin B had a similar issue in May 2002:
http://gcc.gnu.org/ml/gcc-patches/2002-11/msg01661.html
I would like to file a bug report against gcc, and then change
the test script gdb.c++/namespace.exp to XFAIL the test with
stabs+ format and v3 (or later) compilers.
Michael C
next reply other threads:[~2002-12-06 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 16:31 Michael Elizabeth Chastain [this message]
2002-12-05 17:14 ` Daniel Jacobowitz
2002-12-06 11:25 ` David Carlton
2002-12-05 18:06 Michael Elizabeth Chastain
2002-12-06 13:06 Michael Elizabeth Chastain
2002-12-06 17:27 ` David Carlton
2002-12-07 6:49 ` Stan Shebs
2002-12-09 10:59 ` David Carlton
2002-12-06 17:58 ` Daniel Jacobowitz
2002-12-06 19:48 Michael Elizabeth Chastain
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=200212060031.gB60Vt517871@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb@sources.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