From: Guo Ren <guoren@kernel.org>
To: Jim Wilson <jimw@sifive.com>
Cc: jiangshuai_li@c-sky.com, "Maciej Rozycki" <macro@wdc.com>,
"Andrew Burgess" <andrew.burgess@embecosm.com>,
gdb-patches@sourceware.org, 夏立方 <lifang_xia@c-sky.com>,
yunhai_shang <yunhai_shang@c-sky.com>
Subject: Re: [PATCH] riscv: add gdbserver support
Date: Wed, 22 Jan 2020 05:26:00 -0000 [thread overview]
Message-ID: <CAJF2gTSQDb=qZO91x8J7y3gMyJtDLWyKBYKUTd5oX0qars9W+w@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaa7ADP_SmBVoan9AOkWK9parEz5EENZZL5vY+_GcD9SrA@mail.gmail.com>
Hi Jim,
On Tue, Jan 21, 2020 at 7:04 AM Jim Wilson <jimw@sifive.com> wrote:
>
> > 3. vector regitsers r/w
>
> The vector registers are still in draft form, and are subject to
> change. I'd rather not add support for draft features upstream, as
> then we are stuck supporting draft versions of the ISA forever. Also,
> we still don't have a proposal for DWARF register numbers for the
> vector registers.
In fact, both T-HEAD XuanTie C910 and Andes 27-series CPU cores claim
to support vector extensions, which is good for riscv-v extenstion.
Many complex linux vector development/test-suite need linux/gdb/glibc
to support the vector-regs' context.
So I think these basic functions for linux/gdb/glibc should be merged
in advance, rather than waiting for the entire vector spec to freeze.
After all, register save / restore is only a small part of riscv-v and
very basic, maybe the part of registers(abi) could be frozen in the
vector spec in advance.
Here is the linux riscv-v port V2 for task_switch, singal, ptrace: [1]
[1]: https://lore.kernel.org/linux-riscv/20200116143029.31441-4-guoren@kernel.org/
Best Regrads
Guo Ren
next prev parent reply other threads:[~2020-01-22 2:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 5:01 jiangshuai_li
2020-01-20 23:33 ` Jim Wilson
2020-01-21 0:30 ` Maciej W. Rozycki
2020-01-21 2:13 ` Simon Marchi
2020-01-21 2:17 ` Maciej W. Rozycki
2020-01-21 13:01 ` Andrew Burgess
2020-01-21 13:28 ` Andrew Burgess
2020-01-21 13:47 ` Andreas Schwab
2020-01-22 0:11 ` Jim Wilson
2020-01-22 0:45 ` Jim Wilson
2020-01-22 10:19 ` Jim Wilson
2020-01-22 14:08 ` Andrew Burgess
2020-01-21 17:11 ` Maciej W. Rozycki
2020-01-21 23:56 ` Jim Wilson
2020-01-22 5:26 ` Guo Ren [this message]
2020-01-22 6:15 ` Jim Wilson
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='CAJF2gTSQDb=qZO91x8J7y3gMyJtDLWyKBYKUTd5oX0qars9W+w@mail.gmail.com' \
--to=guoren@kernel.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jiangshuai_li@c-sky.com \
--cc=jimw@sifive.com \
--cc=lifang_xia@c-sky.com \
--cc=macro@wdc.com \
--cc=yunhai_shang@c-sky.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).