From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] fix problems with unwinder on mips-irix
Date: Fri, 06 Aug 2004 19:13:00 -0000 [thread overview]
Message-ID: <4113D85B.9040702@gnu.org> (raw)
In-Reply-To: <20040806183121.GS1192@gnat.com>
> Andrew,
>
>
>>> If you've the time, please do.
>>>
>>> Two key things to know:
>>>
>>> - with three unwinders handling three different cases previously handled
>>> by one, there's a lot of dead code paths. For instance,
>>> mips32_heuristic_proc_desc is now only called by mips_insn32_frame_cache
>>> and hence can be inlined there, making it possible for your problem to
>>> be solved more locally.
>>>
>>> - I'm interested in a brutal overhaul of an unwinder, not a small tweak :-)
>
>
> I think I can find the time for "a small tweak" within the next couple
> of weeks, maybe this week-end. But if a "brutal overhaul" is required,
> then the bar is too high for me. I just don't have the time.
I think that you'll find that a brutal overhaul will in the end take
less time than what, at first sight, appears to be just a single simple
wafer thin tweak.
Here we've got what should be a single simple procedure
(mips_insn32_frame_cache) with a very tight interface and an exaustive
testsuite, but instead is anything but.
Can I suggest spending just an hour attacking it, and then posting the
result (just as long as it compiles :-).
Andrew
next prev parent reply other threads:[~2004-08-06 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 1:11 Joel Brobecker
2004-07-30 0:22 ` Andrew Cagney
2004-08-03 4:44 ` Joel Brobecker
2004-08-04 1:43 ` Andrew Cagney
2004-08-06 18:31 ` Joel Brobecker
2004-08-06 19:13 ` Andrew Cagney [this message]
2004-08-30 18:18 ` Joel Brobecker
2004-08-30 19:32 ` Andrew Cagney
2004-08-31 23:44 ` Joel Brobecker
2004-09-01 14:57 ` Andrew Cagney
2004-09-02 23:09 ` Joel Brobecker
2004-09-03 20:17 ` Andrew Cagney
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=4113D85B.9040702@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.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