From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org, macro@imgtec.com
Subject: Re: [PATCH, doc RFA] Remove support for "target m32rsdi" and "target mips/pmon/ddb/rockhopper/lsi"
Date: Tue, 22 Mar 2016 11:54:00 -0000 [thread overview]
Message-ID: <56F13269.8020602@redhat.com> (raw)
In-Reply-To: <8637rivld3.fsf@gmail.com>
On 03/22/2016 10:48 AM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
>> Ref: https://sourceware.org/ml/gdb/2016-03/msg00004.html
>>
>> This removes support for:
>>
>> | target | source |
>> |-------------------+-----------------------|
>> | target m32rsdi | gdb/remote-m32r-sdi.c |
>> | target mips | gdb/remote-mips.c |
>> | target pmon | gdb/remote-mips.c |
>> | target ddb | gdb/remote-mips.c |
>> | target rockhopper | gdb/remote-mips.c |
>> | target lsi | gdb/remote-mips.c |
>>
>> That is:
>>
>> - Remote M32R debugging over SDI.
>>
>> - Debugging boards using the MIPS remote debugging protocol
>> over a serial line, PMON, and a few variants.
>>
>> These are the last non-"target remote" remote targets in the tree, if
>> you don't count "target sim".
>
> I am OK on this, but I'd like to hear what does Maciej (cc'ed) think.
Good idea.
FWIW, I didn't think this would affect MIPS in any way, given that
I couldn't find a single bug report for any of these targets in
bugzilla. I don't mean open bugs, I mean, any, ever, other than
build failure issues. I don't recall anyone mentioning anything
related to these targets on the gdb or gdb-patches lists, ever,
either. It seems like google searches for these targets only hit
the gdb documentation, and my suggestion to remove them on
the gdb@ list [1]. :-)
Also, I thought of MIPS's earlier focus on MDI, and knowing that
even that one was pushed out of tree years ago, my thinking was
that the risk of this affecting anyone in practice
approximates zero.
[1] - https://sourceware.org/ml/gdb/2016-03/msg00004.html
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-03-22 11:54 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 [this message]
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
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=56F13269.8020602@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