From: Xi Ruoyao <xry111@xry111.site>
To: Palmer Dabbelt <palmer@dabbelt.com>, gcc-patches@gcc.gnu.org
Cc: fantasquex@gmail.com, Andrew Waterman <andrew@sifive.com>
Subject: Re: [PATCH v2] RISC-V: Libitm add RISC-V support.
Date: Fri, 28 Oct 2022 12:23:27 +0800 [thread overview]
Message-ID: <f4c97e77124f28c4e3d43da92b4fcd7d52a2f051.camel@xry111.site> (raw)
In-Reply-To: <mhng-9366d3ea-bf38-491e-8318-5fc74e40fd08@palmer-ri-x1c9a>
On Thu, 2022-10-27 at 17:44 -0700, Palmer Dabbelt wrote:
> though I don't have an opinion on whether libitm should be taking ports
> to new targets, I'd never even heard of it before.
I asked this question to myself when I reviewed LoongArch libitm port.
But I remember one maintainer of Deepin (a distro) has complained that
some packages were depending on libitm (and/or libvtv).
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-10-28 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 12:49 Xiongchuan Tan
2022-10-27 23:05 ` Jeff Law
2022-10-28 0:44 ` Palmer Dabbelt
2022-10-28 4:23 ` Xi Ruoyao [this message]
2022-10-29 3:18 ` 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=f4c97e77124f28c4e3d43da92b4fcd7d52a2f051.camel@xry111.site \
--to=xry111@xry111.site \
--cc=andrew@sifive.com \
--cc=fantasquex@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=palmer@dabbelt.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).