lttng-dev Archive mirror
 help / color / mirror / Atom feed
From: Olivier Dion via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] RCU - Bugs in atomic operations for RISC-V with GCC
Date: Thu, 28 Sep 2023 13:09:31 -0400	[thread overview]
Message-ID: <87il7uxm0k.fsf@laura> (raw)

Hi all,

We recently have been informed that the implementation of atomic
operations in GCC for RISC-V have bugs in them [1].  However, the fixing
patches missed the 13.2 release and it does not seem that they have been
back-ported to other versions yet.

For this reasons, we concur that it was best to mark Userspace RCU as
broken for RISC-V when compiling with GCC.  However, it is still
possible to compile Userspace RCU for RISC-V with other toolchains such
as Clang.

Cheers,
Olivier

[1] https://review.lttng.org/c/userspace-rcu/+/10942

-- 
Olivier Dion
EfficiOS Inc.
https://www.efficios.com

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

                 reply	other threads:[~2023-09-28 17:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87il7uxm0k.fsf@laura \
    --to=lttng-dev@lists.lttng.org \
    --cc=odion@efficios.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).