From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] minsyms.c: Fix switching to GNU v3 ABI
Date: Sun, 28 Mar 2004 18:28:00 -0000 [thread overview]
Message-ID: <vt2zna0ltcd.fsf@zenia.home> (raw)
In-Reply-To: <20040326113928.GG17229@cygbert.vinschen.de>
Corinna Vinschen <vinschen@redhat.com> writes:
> On Mar 25 15:44, Jim Blandy wrote:
> > One comment: I notice that we actually remove the leading character
> > earlier in prim_record_minimal_symbol_and_info, to check if the name
> > is the same as that of the GCC compilation marker symbol. It would be
> > nicer if we could just remove the leading character once, at the top
> > of the function, and then simplify the the "__gnu_compiled" test.
> > Doing so shouldn't interfere with the GCC_COMPILED_FLAG_SYMBOL tests,
> > since the code already presumes those both start with 'g'.
>
> Well, it could interfere. Assuming that leading char is the underscore.
> The first test would now find "gcc_compiled.", but not "_gcc_compiled.".
> When skipping the leading char before testing, the same test would now
> also find "_gcc_compiled.". If that's ok, I don't have a problem to
> change it as you like. Otherwise, I'd propose the below patch, which
> avoids that problem.
Sure, this looks good; it leaves the current behavior unchanged.
Please commit.
I'm kind of amazed that some of the GCC compilation symbols get
prefixed, while others don't. That exact arrangement --- where
GCC_COMPILED_FLAG_SYMBOL and GCC2_COMPILED_FLAG_SYMBOL are tested
before stripping the leading char, and __gnu_compiled is tested after
stripping --- originated in 1993 in dbxread.c, and was later moved to
minsyms.c:
Wed Jul 28 13:19:34 1993 Jim Kingdon (kingdon@lioth.cygnus.com)
* config/mips/xm-mips.h: Define HAVE_TERMIOS.
* dbxread.c (record_minimal_symbol): Don't put gcc_compiled or
__gnu_compiled* symbols into the minimal symbols.
(dbxread.c 1.153 in the internal Red Hat repository). There's no
indication of why the distinction is made. But it does seem to have
been done deliberately, rather than being the unintentional result of
accreted changes. So I guess we should leave it as is. I'll stick a
note in there after you've committed.
next prev parent reply other threads:[~2004-03-28 18:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Corinna Vinschen
2004-03-10 10:57 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-10 15:08 ` Daniel Jacobowitz
2004-03-10 15:55 ` Corinna Vinschen
2004-03-10 16:04 ` Daniel Jacobowitz
2004-03-10 16:16 ` Corinna Vinschen
2004-03-19 0:09 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-10 16:20 ` Daniel Jacobowitz
2004-03-19 0:09 ` Corinna Vinschen
2004-03-10 16:34 ` Corinna Vinschen
2004-03-10 16:37 ` Daniel Jacobowitz
2004-03-10 17:54 ` Corinna Vinschen
2004-03-10 18:02 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-10 18:23 ` Corinna Vinschen
2004-03-19 0:09 ` Corinna Vinschen
2004-03-22 17:34 ` Corinna Vinschen
2004-03-22 17:38 ` Corinna Vinschen
2004-03-25 20:44 ` Jim Blandy
2004-03-26 13:57 ` Corinna Vinschen
2004-03-26 17:54 ` Eli Zaretskii
2004-03-28 18:28 ` Jim Blandy [this message]
2004-03-29 11:26 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-10 18:20 ` Daniel Jacobowitz
2004-03-19 0:09 ` Ian Lance Taylor
2004-03-10 18:30 ` Ian Lance Taylor
2004-03-19 0:09 ` Corinna Vinschen
2004-03-10 18:46 ` Corinna Vinschen
2004-03-10 19:02 ` Ian Lance Taylor
2004-03-19 0:09 ` Ian Lance Taylor
2004-03-19 0:09 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-10 16:43 ` Corinna Vinschen
2004-03-10 16:46 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Corinna Vinschen
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Corinna Vinschen
2004-03-19 0:09 ` Jim Blandy
2004-03-10 15:04 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2004-03-10 18:03 Michael Elizabeth Chastain
2004-03-19 0:09 ` 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=vt2zna0ltcd.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@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