From: Luis Machado <luis.machado@arm.com>
To: Simon Marchi <simark@simark.ca>,
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: Tue, 26 Nov 2024 08:38:34 +0000 [thread overview]
Message-ID: <e66549f9-48fc-4871-bc01-dda573fdad88@arm.com> (raw)
In-Reply-To: <9666dcc3-cdad-4c1d-8c8a-8bb4cc6b1ec7@simark.ca>
On 11/26/24 03:41, Simon Marchi wrote:
>
>
> 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
Thanks for the patch 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
I agree with your assessment. We might want to mention the last gdb version
supporting this target on the NEWS, but otherwise seems like a good cleanup
and it would be nice to do it alongside binutils.
next prev parent reply other threads:[~2024-11-26 8:39 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
2024-11-26 8:38 ` Luis Machado [this message]
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=e66549f9-48fc-4871-bc01-dda573fdad88@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyao@sourceware.org \
--cc=simark@simark.ca \
--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