From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ezannoni@redhat.com, nickc@redhat.com,
gdb-patches@sources.redhat.com, rearnsha@arm.com
Subject: Re: [PATCH/RFC] coffread.c: delete param
Date: Wed, 15 Oct 2003 16:37:00 -0000 [thread overview]
Message-ID: <16269.31369.339106.180129@localhost.redhat.com> (raw)
In-Reply-To: <200310151626.h9FGQKBZ021297@duracef.shout.net>
Michael Elizabeth Chastain writes:
> Nickc writes:
> > Given Andrew's comment in the code, I would be rather wary of this
> > patch. Presumably there is some good reason for passing the
> > cs->c_sclass field in the (void *) pointer argument slot, or otherwise
> > Andrew would not have gone to all that trouble of casting it.
>
> I figured out some of the history:
>
> Back in gdb 4.17, arm_pc_is_thumb in arm-tdep.c used this c_sclass
> information to determine whether a symbol is a Thumb or Arm function.
> gdb 4.18 rewrote arm_pc_is_thumb with a new mechanism based on
> COFF_MAKE_MSYMBOL_SPECIAL, which sets a flag bit instead of storing the
> sclass and reading it later. That enables other readers besides the
> coff reader to mark functions as special (ELF_MAKE_MSYMBOL_SPECIAL
> in particular).
>
> The change from 4.17 to 4.18 added the new COFF_MAKE_MSYMBOL_SPECIAL,
> and changed arm-tdep.c to use the new COFF_MAKE_MSYMBOL_SPECIAL,
> but did not delete the old dangling c_sclass code.
>
> Someone with access to the old Cygnus CVS repository might be able
> to say more about the exact change some time between 4.17 and 4.18.
Did you see my posting with the exact diffs (from 1998) I posted
yesterday?
http://sources.redhat.com/ml/gdb-patches/2003-10/msg00470.html
That explains in detail what happened, which is pretty much how you
describe it here.
elena
>
> Andrew C came along a few years later and added a cast just to make
> the compiler happy -- just an innocent janitor.
>
> It's very unlikely that Elena's change will change the behavior of gdb.
> This c_sclass info has been dead since 4.18, replaced by
> COFF_MAKE_MSYMBOL_SPECIAL.
>
> It would be nice if someone could build and test arm-coff to verify
> this line of reasoning. But, it's also nice to know the history,
> which explains why c_sclass is stored, but never read.
>
> > Does it improve things ? :-) If so, what ?
>
> It's part of a cleanup for the msymbol.info field.
>
> There are three different places in gdb which use msymbol.info.
> This is one of them. The improvement is that getting rid
> of dead code makes it simpler to talk about the other two places.
>
> Michael C
next prev parent reply other threads:[~2003-10-15 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 16:26 Michael Elizabeth Chastain
2003-10-15 16:37 ` Elena Zannoni [this message]
2003-10-15 16:47 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-10-14 21:41 Elena Zannoni
2003-10-15 8:56 ` Richard Earnshaw
2003-10-15 15:10 ` Andrew Cagney
2003-10-15 15:25 ` Nick Clifton
2003-10-15 15:39 ` Andrew Cagney
2003-10-15 15:59 ` Elena Zannoni
2003-11-05 15:30 ` Elena Zannoni
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=16269.31369.339106.180129@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
--cc=nickc@redhat.com \
--cc=rearnsha@arm.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