From: Pedro Alves <palves@redhat.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: 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: Mon, 02 May 2016 11:59:00 -0000 [thread overview]
Message-ID: <a378644c-b0a4-50eb-2fe9-fe046b5af145@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1604020049090.21372@tp.orcam.me.uk>
On 04/02/2016 12:57 AM, Maciej W. Rozycki wrote:
> On Thu, 31 Mar 2016, Pedro Alves wrote:
>
>> I'll push the patch in in a bit.
>
> NB it looks to me `mips_r3041_reg_names' is now dead. We just *might*
> consider rewiring it like `mips_tx39_reg_names', but that would require
> defining another BFD machine type and I doubt anybody cares about the
> R3041 anymore (cf. the relevant comment you've just removed). So if you
> care to remove it too, then I'll appreciate it and a change to do so is
> preapproved.
>
> Given that the variable is static I wonder why it hasn't triggered a
> compilation error in the build actually.
That's because gdb doesn't use -Wunused presently.
I never managed to come back to this, and looks like we won't need to.
Trevor sent a patch that removes mips_r3041_reg_names among a ton
of other unused variables, here:
https://sourceware.org/ml/gdb-patches/2016-04/msg00664.html
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-05-02 11:59 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 [this message]
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
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=a378644c-b0a4-50eb-2fe9-fe046b5af145@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@imgtec.com \
--cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).