From: Xi Ruoyao <xry111@mengyan1223.wang>
To: Satish Vasudeva <satish.vasudeva@cohesity.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Libatomic 16B
Date: Fri, 25 Feb 2022 04:05:28 +0800 [thread overview]
Message-ID: <1bb8ab09556727917d07ec31683996bb7e493fa6.camel@mengyan1223.wang> (raw)
In-Reply-To: <CABp-VvJDTMyZedDnVKyn1q5oy5TkOGF5Ui=EKoBYnPVwp9vFxQ@mail.gmail.com>
On Thu, 2022-02-24 at 11:35 -0800, Satish Vasudeva wrote:
> Thanks for the response.
>
> Looking further into libatomic library code, I do see 16B move
> instructions have been used for atomic_exchange code like below. Just
> wondering why it is not generating a intrinsic __atomic_load_16 using
> this instruction.
>
> movdqa0x0(%rbp),%xmm0
Because both Intel and AMD have not claimed "this is atomic". In
__atomic_exchange movdqa is used as a normal data move instruction
(actually, GCC optimized memcpy calls in libatomic code to this).
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-02-24 20:05 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 [this message]
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
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=1bb8ab09556727917d07ec31683996bb7e493fa6.camel@mengyan1223.wang \
--to=xry111@mengyan1223.wang \
--cc=gcc-help@gcc.gnu.org \
--cc=satish.vasudeva@cohesity.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).