On Wed, May 20, 2026 at 4:34 AM Dmitry Baryshkov via lists.openembedded.org
<[email protected]> wrote:
> Building mariadb for ARMv8.3-A and later, fails with:
>
> Assembler messages:
> {standard input}:169: Error: selected processor does not support `retaa'
> {standard input}:271: Error: selected processor does not support `retaa'
>
> It happens because the pmem_cvap() funciton manually inserts the `.arch
> armv8-2.a` clause, making GAS believe that retaa instruction (inserted
> by GCC) is invalid. Bump the manually inserted clause to armv8.3-a, to
> prevent GAS from choking on the retaa instructions.
>
> Signed-off-by: Dmitry Baryshkov <[email protected]>
> ---
> meta-oe/recipes-dbs/mysql/mariadb.inc | 1 +
> ...-sync-cache.cc-bump-ARMv8-arch-to-AR.patch | 35 +++++++++++++++++++
> 2 files changed, 36 insertions(+)
> create mode 100644
> meta-oe/recipes-dbs/mysql/mariadb/0001-storage-innobase-sync-cache.cc-bump-ARMv8-arch-to-AR.patch
>
> diff --git a/meta-oe/recipes-dbs/mysql/mariadb.inc
> b/meta-oe/recipes-dbs/mysql/mariadb.inc
> index 9470184d3d43..456c1e1354e8 100644
> --- a/meta-oe/recipes-dbs/mysql/mariadb.inc
> +++ b/meta-oe/recipes-dbs/mysql/mariadb.inc
> @@ -25,6 +25,7 @@ SRC_URI = "
> https://archive.mariadb.org/${BP}/source/${BP}.tar.gz \
> file://riscv32.patch \
> file://0001-support-reproducible-builds.patch \
>
> file://0001-storage-mroonga-CMakeLists.txt-fix-reproducible-buil.patch \
> +
> file://0001-storage-innobase-sync-cache.cc-bump-ARMv8-arch-to-AR.patch \
> "
> SRC_URI[sha256sum] =
> "14783ddc5edd966ff05aa0efd5ed6d3d369ed5b9e4080a448f00f87a9f0a4a6b"
>
> diff --git
> a/meta-oe/recipes-dbs/mysql/mariadb/0001-storage-innobase-sync-cache.cc-bump-ARMv8-arch-to-AR.patch
> b/meta-oe/recipes-dbs/mysql/mariadb/0001-storage-innobase-sync-cache.cc-bump-ARMv8-arch-to-AR.patch
> new file mode 100644
> index 000000000000..dfb6c7795407
> --- /dev/null
> +++
> b/meta-oe/recipes-dbs/mysql/mariadb/0001-storage-innobase-sync-cache.cc-bump-ARMv8-arch-to-AR.patch
> @@ -0,0 +1,35 @@
> +From ac6553ff3a21eb048f623081b7b7e31e43d38d77 Mon Sep 17 00:00:00 2001
> +From: Dmitry Baryshkov <[email protected]>
> +Date: Wed, 20 May 2026 14:14:02 +0300
> +Subject: [PATCH] storage/innobase/sync/cache.cc: bump ARMv8 arch to
> ARMv8.3
> +
> +Building for ARMv8.3-A and later, fails with:
> +
> +Assembler messages:
> +{standard input}:169: Error: selected processor does not support `retaa'
> +{standard input}:271: Error: selected processor does not support `retaa'
> +
> +It happens because the pmem_cvap() funciton manually inserts the `.arch
> +armv8-2.a` clause, making GAS believe that retaa instruction (inserted
> +by GCC) is invalid. Bump the manually inserted clause to armv8.3-a, to
> +prevent GAS from choking on the retaa instructions.
> +
> +Upstream-Status: Inappropriate [upstream ticket
> https://github.com/MariaDB/server/pull/3677#issuecomment-4497763227]
>
I think you can say 'Submitted [https://github.com/MariaDB/server/pull/5105]'
now.
> +Signed-off-by: Dmitry Baryshkov <[email protected]>
> +---
> + storage/innobase/sync/cache.cc | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/storage/innobase/sync/cache.cc
> b/storage/innobase/sync/cache.cc
> +index c5e67709e22b..104a45cee9ee 100644
> +--- a/storage/innobase/sync/cache.cc
> ++++ b/storage/innobase/sync/cache.cc
> +@@ -85,7 +85,7 @@ static void pmem_cvap(const void* buf, size_t size)
> + #if defined __ARM_ARCH && __ARM_ARCH == 9
> + __asm__ __volatile__(".arch armv9.4-a\n dc cvap, %0" :: "r"(u) :
> "memory");
> + #else
> +- __asm__ __volatile__(".arch armv8.2-a\n dc cvap, %0" :: "r"(u) :
> "memory");
> ++ __asm__ __volatile__(".arch armv8.3-a\n dc cvap, %0" :: "r"(u) :
> "memory");
> + #endif
> +
> + __asm__ __volatile__("dmb ishst" ::: "memory");
> --
> 2.47.3
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#127127):
https://lists.openembedded.org/g/openembedded-devel/message/127127
Mute This Topic: https://lists.openembedded.org/mt/119406181/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
