From: Michael Elizabeth Chastain <mec@shout.net>
To: geoffk@apple.com
Cc: gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: C ASSEMBLER_NAME patch
Date: Sat, 26 Jul 2003 16:04:00 -0000 [thread overview]
Message-ID: <200307261604.h6QG4LJF021434@duracef.shout.net> (raw)
Geoff K writes:
> This is supposed to happen under some circumstances. (Not the
> circumstances that you're experiencing---I'm fixing that now---but some
> other circumstances.)
>
> How should GCC emit stabs so that GDB does the right thing with these
> symbol names?
I'm not an expert on this, so I hope one of the symtab people
(Daniel J) will correct me if I get this wrong:
Names at file scope should not be qualified with ".number", and names at
function scope can be qualified.
The comment in lhd_set_decl_assembler_name says that is what it's doing
("Can't just use the variable's own name for a variable whose scope is
less than the whole compilation.") so it looks like the test just needs
to be adjusted, to my superficial eyes.
We have a test (gdb.base/scope.exp) with lots of function-scoped and
block-scoped static variables, and they are getting qualified,
and gdb handles them properly. It's only these file-scope symbols that
are hurting, and that happens just when a prototype is visible.
That is:
static void f1 ();
static void f1 () { return; }
static void f2 () { return; }
f1 is getting qualified (bad) and f2 is not (good).
Thanks,
Michael C
next reply other threads:[~2003-07-26 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 16:04 Michael Elizabeth Chastain [this message]
2003-07-26 21:51 ` Geoffrey Keating
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=200307261604.h6QG4LJF021434@duracef.shout.net \
--to=mec@shout.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=geoffk@apple.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).