From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>
Cc: Pedro Alves <palves@redhat.com>,
Trevor Saunders <tbsaunde+binutils@tbsaunde.org>,
Yao Qi <qiyaoltc@gmail.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH, doc RFA] Remove support for "target m32rsdi" and "target mips/pmon/ddb/rockhopper/lsi"
Date: Wed, 04 May 2016 01:03:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1605040154010.6794@tp.orcam.me.uk> (raw)
In-Reply-To: <20160503235813.GA4366@tsaunders-iceball.corp.tor1.mozilla.com>
On Wed, 4 May 2016, Trevor Saunders wrote:
> > > Especially the heuristic
> > > unwinder bits look highly suspicious to me, where the variable is updated
> > > as the analysis proceeds. It could be that these variables can indeed go,
> > > but perhaps something is missing that should be there.
>
> perhaps, my guess is that it was necessary at one time, but isn't
> anymore.
That can be tracked down rather easily now that we have GIT rather than
CVS driving our repository, but I'm more concerned they might be symptoms
of unfinished or buggy code. This is hairy stuff (by definition, actually
-- where there's no DWARF information available we should try PDR records
first, where available, before resorting, in desperation, to heuristics).
Maciej
prev parent reply other threads:[~2016-05-04 1:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 16:00 Pedro Alves
2016-03-22 10:49 ` Yao Qi
2016-03-22 11:54 ` Pedro Alves
2016-03-30 22:19 ` Maciej W. Rozycki
2016-03-31 12:07 ` Pedro Alves
2016-04-02 0:00 ` Maciej W. Rozycki
2016-05-02 11:59 ` Pedro Alves
2016-05-03 14:57 ` Maciej W. Rozycki
2016-05-03 18:59 ` Pedro Alves
2016-05-04 0:33 ` Trevor Saunders
2016-05-04 1:03 ` Maciej W. Rozycki [this message]
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=alpine.DEB.2.00.1605040154010.6794@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
--cc=tbsaunde+binutils@tbsaunde.org \
--cc=tbsaunde@tbsaunde.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).