From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] remove ECOFF
Date: Mon, 19 Aug 2013 23:22:00 -0000 [thread overview]
Message-ID: <5212A898.3010606@earthlink.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1308191948550.8514@tp.orcam.me.uk>
On 8/19/13 2:20 PM, Maciej W. Rozycki wrote:
> On Mon, 19 Aug 2013, Tom Tromey wrote:
>
>> The others are in mips_find_abi_section. I don't know what the impact
>> would be of removing this code, so I did not touch it.
>
> The MIPS target wants to use minimal ECOFF debug information that is
> stored in ELF binaries in the so called PDR or Procedure Descriptor Record
> section [1].
mdebugread.c is a lot of code to maintain for just this one use. Would
it be possible to do a selective restore of the section reader when you
bring back the rest of PDR handling?
Right now mdebugread.c is unknowingly getting more and more broken (no
way to test PDR regressions because there is no code using it now,
right?), and so your revival plan is going to be complicated by having
to figure out which generic patches need to be undone.
Another possible bonus is that a future redesigned PDR reader can be
more on-demand, only activate if one needs prologue analysis and DWARF
info is missing.
Stan
stan@codesourcery.com
next prev parent reply other threads:[~2013-08-19 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 18:19 Tom Tromey
2013-08-19 18:51 ` Mark Kettenis
2013-08-19 18:57 ` Tom Tromey
2013-08-19 19:02 ` Tom Tromey
2013-08-19 19:41 ` Joel Brobecker
2013-08-19 21:21 ` Maciej W. Rozycki
2013-08-19 23:22 ` Stan Shebs [this message]
2013-08-20 15:12 ` Tom Tromey
2013-08-20 15:20 ` Mark Kettenis
2013-08-20 16:19 ` Maciej W. Rozycki
2013-08-20 15:19 ` Joseph S. Myers
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=5212A898.3010606@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.org \
/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