From: Simon Marchi <simark@simark.ca>
To: Luis Machado <luis.machado@arm.com>,
Pedro Alves <pedro@palves.net>, John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org,
David Spickett <David.Spickett@arm.com>
Subject: Re: [PATCH] [Arm] Remove dead FPA code
Date: Mon, 14 Nov 2022 09:30:09 -0500 [thread overview]
Message-ID: <7dfb55ee-6663-f326-ddaa-1ee09e1551d0@simark.ca> (raw)
In-Reply-To: <ff30980f-86db-281c-bd60-de214cee087c@arm.com>
> Do you want that procedure followed completely, including the week waiting? I also seem to recall a different policy, where we
> deprecate something for a particular release and then remove on the next one.
Given how obsolete FPA is, I would be fine with removing it in this
release. It would be good practice to send an announcement on
gdb-announce, like the wiki says. We don't do it often, but if we did
it often, perhaps we'd be less scared of doing it, it would become more
a routine thing.
I agree with Pedro that this patch should ideally not change the
register layout for when not using XML. However, it's also fine to have
a plan to stop supporting non-XML-using targets eventually, if that's
what we want.
Simon
next prev parent reply other threads:[~2022-11-14 14:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 12:30 Luis Machado
2022-09-20 12:47 ` Eli Zaretskii
2022-10-02 13:39 ` Enze Li
2022-10-03 8:27 ` Luis Machado
2022-10-03 17:33 ` John Baldwin
2022-10-03 19:16 ` Pedro Alves
2022-10-04 8:43 ` Luis Machado
2022-10-04 17:08 ` John Baldwin
2022-10-04 17:43 ` Luis Machado
2022-10-04 21:36 ` John Baldwin
2022-10-05 8:26 ` Luis Machado
2022-10-05 8:36 ` David Spickett
2022-10-05 8:36 ` David Spickett
2022-10-05 16:48 ` John Baldwin
2022-10-05 16:57 ` Richard Earnshaw
2022-10-06 13:02 ` Luis Machado
2022-10-10 14:58 ` Pedro Alves
2022-10-13 7:23 ` Luis Machado
2022-10-13 8:29 ` Pedro Alves
2022-10-13 9:40 ` Luis Machado
2022-10-25 13:54 ` Luis Machado
2022-11-14 14:30 ` Simon Marchi [this message]
2022-10-10 14:56 ` Pedro Alves
2022-10-13 7:18 ` Luis Machado
2022-10-13 8:44 ` Pedro Alves
2022-10-13 9:15 ` Luis Machado
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=7dfb55ee-6663-f326-ddaa-1ee09e1551d0@simark.ca \
--to=simark@simark.ca \
--cc=David.Spickett@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=luis.machado@arm.com \
--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).