From: Chung-Ju Wu <jasonwucj@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>, GCC Mailing List <gcc@gcc.gnu.org>
Cc: Kuan-Lin Chen <kuanlinchentw@gmail.com>,
Yan-Ting Lin <lessatecir@gmail.com>,
Hsiangkai Wang <hsiangkai@gmail.com>,
Wei-cheng Wang <cole945@gmail.com>
Subject: Re: Deprecating nds32-*-linux-* target for GCC 14 (and removing it for GCC 15)
Date: Thu, 14 Dec 2023 14:25:50 +0800 [thread overview]
Message-ID: <bbdeab5f-6086-4eb1-abe6-02c4fd75e563@gmail.com> (raw)
In-Reply-To: <e4e7eb78-736c-457d-9680-0cc470083a42@gmail.com>
On 2023/12/12 07:43 UTC+8, Jeff Law via Gcc wrote:
>
>
> On 12/11/23 16:19, Andrew Pinski via Gcc wrote:
>> nds32 support in Linux was removed last year:
>> https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
>>
>> The support for glibc never made it upstream as far as I can tell either.
>>
>> What are others thoughts on this?
> I believe the architecture is dead, so I wouldn't lose any sleep if it got deprecated across the board. While my tester includes nds32le-elf and nds32be-elf, there's no gdbsim, so those targets don't provide much, if any, additional coverage over targets in the tester.
>
> Jeff
Hi Jeff,
As for gdbsim/openocd, I remember that we did have nds32 contributions previously:
- gdb: http://sourceware.org/ml/gdb-patches/2013-07/msg00223.html
- openocd: http://openocd.zylin.com/1259
I suppose they have recently been dropped from the current gdb/openocd repository
due to the lack of maintenance. I will reach out to Andes members to inquire whether
the architecture is still considered to be available in gdb/openocd.
Regards,
jasonwucj
next prev parent reply other threads:[~2023-12-14 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 23:19 Andrew Pinski
2023-12-11 23:31 ` Joel Sherrill
2023-12-11 23:43 ` Jeff Law
2023-12-14 6:00 ` Chung-Ju Wu
2023-12-14 6:25 ` Chung-Ju Wu [this message]
2023-12-14 14:28 ` Jeff Law
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=bbdeab5f-6086-4eb1-abe6-02c4fd75e563@gmail.com \
--to=jasonwucj@gmail.com \
--cc=cole945@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hsiangkai@gmail.com \
--cc=jeffreyalaw@gmail.com \
--cc=kuanlinchentw@gmail.com \
--cc=lessatecir@gmail.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).