From: Simon Marchi <simark@simark.ca>
To: Sandra Loosemore <sloosemore@baylibre.com>, gdb-patches@sourceware.org
Cc: qiyao@sourceware.org
Subject: Re: [RFA][PATCH] Remove gdb support for Nios II target
Date: Mon, 25 Nov 2024 22:41:25 -0500 [thread overview]
Message-ID: <9666dcc3-cdad-4c1d-8c8a-8bb4cc6b1ec7@simark.ca> (raw)
In-Reply-To: <b5369602-1793-48b4-a466-643d40f2be9a@baylibre.com>
On 2024-11-25 16:12, Sandra Loosemore wrote:
> The attached patch removes gdb support for the Nios II target, which has been EOL'ed by the vendor. I've already pushed the patch to remove support from GCC:
>
> https://gcc.gnu.org/pipermail/gcc-cvs/2024-November/413482.html
>
> I've also got a separate binutils patch I'm about to post and I'd like to get them both in at the same time.
>
> Can someone approve this patch? I'm not actually the gdb maintainer for this target; Yao Qi is listed but hasn't been active in a while.
>
> -Sandra
The patch LGTM, I just can't remember or find what's our policy for
this, how much time we want to keep support for a target after gcc has
dropped support for it.
The last gcc release with support for it was gcc 14, released in May
2024. gdb 15 was released in July 2024. So if we want to have at least
one gdb release after the last gcc supporting a given arch, we already
have it, meaning this patch could be merged right away (I would be fine
with that).
Can someone else give a second opinion?
Simon
next prev parent reply other threads:[~2024-11-26 3:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 21:12 Sandra Loosemore
2024-11-26 3:41 ` Simon Marchi [this message]
2024-11-26 8:38 ` Luis Machado
2024-11-26 11:04 ` Tom de Vries
2024-11-27 18:19 ` Kevin Buettner
2024-11-28 11:34 ` 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=9666dcc3-cdad-4c1d-8c8a-8bb4cc6b1ec7@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=qiyao@sourceware.org \
--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