From: Jeff Law <jeffreyalaw@gmail.com>
To: Chung-Ju Wu <jasonwucj@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 07:28:31 -0700 [thread overview]
Message-ID: <d26f7fd6-8914-4f46-a446-44dc714f33f7@gmail.com> (raw)
In-Reply-To: <bbdeab5f-6086-4eb1-abe6-02c4fd75e563@gmail.com>
On 12/13/23 23:25, Chung-Ju Wu wrote:
>
> 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.
I don't see evidence that the sim patch ever got reviewed. Given it's
~10 years old, it'd probably need some work to be brought up to current
standards. If someone wanted to tackle that, it would be great.
Basically I just wanted to note that as it stands right now, while nds32
is included in the tester's configurations, the lack of a simulator does
limit how much benefit we get from including nds32.
jeff
prev parent reply other threads:[~2023-12-14 14:28 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
2023-12-14 14:28 ` Jeff Law [this message]
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=d26f7fd6-8914-4f46-a446-44dc714f33f7@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=cole945@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hsiangkai@gmail.com \
--cc=jasonwucj@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).