From: Florian Weimer <fweimer@redhat.com>
To: Satish Vasudeva <satish.vasudeva@cohesity.com>
Cc: Xi Ruoyao <xry111@mengyan1223.wang>,
Stefan Ring <stefanrin@gmail.com>,
Xi Ruoyao via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Libatomic 16B
Date: Wed, 02 Mar 2022 06:55:56 +0100 [thread overview]
Message-ID: <87zgm8kidv.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CABp-VvKz+in-UJQWp0HoyAB67RQh19j29eKi1BmVw7aAp23G+g@mail.gmail.com> (Satish Vasudeva's message of "Tue, 1 Mar 2022 16:16:29 -0800")
* Satish Vasudeva:
> Looking back at the description in
> https://gcc.gnu.org/legacy-ml/gcc-patches/2017-01/msg02344.html It
> sounds like CAS based implementation is a problem for volatile atomic
> loads. Can any one please elaborate what is the issue with volatile
> atomic loads. I am trying to do risk analysis in our code.
The page could be mapped read-only (say if it's in memory shared across
processes). Reading such values using CAS will fault, so CAS is not a
full replacement.
Thanks,
Florian
prev parent reply other threads:[~2022-03-02 5:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 16:42 Satish Vasudeva
2022-02-24 16:42 ` Satish Vasudeva
2022-02-25 13:53 ` Florian Weimer
2022-02-24 19:09 ` Xi Ruoyao
2022-02-24 19:35 ` Satish Vasudeva
2022-02-24 20:05 ` Xi Ruoyao
2022-02-24 20:13 ` Segher Boessenkool
2022-02-24 20:38 ` Satish Vasudeva
2022-02-25 8:35 ` Stefan Ring
2022-02-25 8:48 ` Xi Ruoyao
2022-02-25 14:01 ` Florian Weimer
2022-02-25 14:10 ` Alexander Monakov
2022-02-25 14:16 ` Xi Ruoyao
2022-02-25 14:25 ` Xi Ruoyao
2022-02-25 17:05 ` Satish Vasudeva
2022-02-25 17:16 ` Xi Ruoyao
2022-02-25 17:25 ` Satish Vasudeva
2022-03-02 0:16 ` Satish Vasudeva
2022-03-02 5:55 ` Florian Weimer [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=87zgm8kidv.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=satish.vasudeva@cohesity.com \
--cc=stefanrin@gmail.com \
--cc=xry111@mengyan1223.wang \
/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).