Declare PG_HAVE_8BYTE_SINGLE_COPY_ATOMICITY for aarch64

From: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Declare PG_HAVE_8BYTE_SINGLE_COPY_ATOMICITY for aarch64
Date: 2022-03-16 12:32:35
Message-ID: f7f3f0febe27862711f924a7b0f39e065e547f4b.camel@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Good day, hackers.

Architecture Reference Manual for ARMv8 B2.2.1 [1] states:

For explicit memory effects generated from an Exception level the
following rules apply:
- A read that is generated by a load instruction that loads a single
general-purpose register and is aligned to the size of the read in the
instruction is single-copy atomic.
- A write that is generated by a store instruction that stores a single
general-purpose register and is aligned to the size of the write in the
instruction is single-copy atomic.

So I believe it is safe to define PG_HAVE_8BYTE_SINGLE_COPY_ATOMICITY
for aarch64

[1] https://documentation-service.arm.com/static/61fbe8f4fa8173727a1b734e
https://developer.arm.com/documentation/ddi0487/latest

-------

regards

Yura Sokolov
Postgres Professional
y(dot)sokolov(at)postgrespro(dot)ru
funny(dot)falcon(at)gmail(dot)com

Attachment Content-Type Size
v0-0001-Declare-aarch64-has-single-copy-atomicity-for-8-b.patch text/x-patch 1.5 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2022-03-16 12:47:15 Re: ExecTypeSetColNames is fundamentally broken
Previous Message Amit Kapila 2022-03-16 11:51:48 Re: Issue with pg_stat_subscription_stats