From: Luis Machado <luis.machado@arm.com>
To: "Sandra Loosemore" <sloosemore@baylibre.com>,
"Moritz Strübe" <moritz.struebe@siemens-energy.com>,
gdb-patches@sourceware.org
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 1/2] Nios2, libbfd: Support new coredump .reg section
Date: Tue, 23 Apr 2024 16:32:39 +0100 [thread overview]
Message-ID: <6e31b4c7-1970-48d7-b29a-195a071c4ec6@arm.com> (raw)
In-Reply-To: <31f3077c-2fe1-49c2-b100-d596ab644a22@baylibre.com>
On 4/23/24 15:51, Sandra Loosemore wrote:
> On 4/23/24 07:28, Luis Machado wrote:
>> Hi,
>>
>> I just spotted Sandra's message [1] about nios2 deprecation.
>>
>> Do we have plans for deprecating such support in binutils/gdb as well, for the
>> sake of reducing future maintenance burden?
>
> Yes, I plan to take care of producing patches to remove the nios2 port entirely from binutils/gdb, as well as from gcc, a little bit farther down the line. I'm not sure of the best timing with respect to upcoming releases, and at the moment I am swamped with other tasks anyway, but it's definitely on my list of things to do -- I don't want to leave this as a pointless maintenance burden for others.
>
> -Sandra
Great. Thanks for the update Sandra.
next prev parent reply other threads:[~2024-04-23 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240419103922.3621961-1-moritz.struebe@siemens-energy.com>
2024-04-19 10:39 ` Moritz Strübe
2024-04-19 15:06 ` Tom Tromey
2024-04-23 13:28 ` Luis Machado
2024-04-23 14:51 ` Sandra Loosemore
2024-04-23 15:31 ` Simon Marchi
2024-04-23 15:32 ` Luis Machado [this message]
2024-04-19 10:39 ` [PATCH 2/2] Nios2, gdb: Adjust to new coredump format Moritz Strübe
2024-04-19 15:08 ` Tom Tromey
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=6e31b4c7-1970-48d7-b29a-195a071c4ec6@arm.com \
--to=luis.machado@arm.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=moritz.struebe@siemens-energy.com \
--cc=sloosemore@baylibre.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).