From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Remove support for S+core
Date: Wed, 16 Mar 2022 10:28:41 -0600 [thread overview]
Message-ID: <87a6dpkgjq.fsf@tromey.com> (raw)
In-Reply-To: <c558f159-e982-775d-ea2b-9dd3cd8ccff0@palves.net> (Pedro Alves's message of "Wed, 16 Mar 2022 14:44:18 +0000")
Pedro> I think we should just drop the whole score port, though. See here, from 2014 (!):
gdb has warped my perspective so much that my first thought was that
this seems kind of recent.
Pedro> Like so. Given this has been removed from GCC for so long, and we never heard
Pedro> of anyone using the port or file a bug report about it all these years, I think
Pedro> we can just go ahead and delete it without a deprecation period.
Agreed.
Tom
next prev parent reply other threads:[~2022-03-16 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 22:31 [PATCH] Remove 'target_mach' global from score-tdep.c Tom Tromey
2022-03-16 11:38 ` Andrew Burgess
2022-03-16 12:07 ` Pedro Alves
2022-03-16 14:44 ` [PATCH] gdb: Remove support for S+core Pedro Alves
2022-03-16 15:55 ` Andrew Burgess
2022-03-16 16:28 ` Tom Tromey [this message]
2022-03-17 15:42 ` Pedro Alves
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=87a6dpkgjq.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).