From: <daniel.turull@ericsson.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Daniel Turull <daniel.turull@ericsson.com>
Subject: [scarthgap][PATCH 7/9] libatomic-ops: upgrade 7.8.2 -> 7.8.4
Date: Thu, 9 Apr 2026 11:29:34 +0200 [thread overview]
Message-ID: <20260409092936.1740143-8-daniel.turull@ericsson.com> (raw)
In-Reply-To: <20260409092936.1740143-1-daniel.turull@ericsson.com>
From: Daniel Turull <daniel.turull@ericsson.com>
Changelog for libatomic-ops: 7.8.2 -> 7.8.4
============================================================
== [7.8.4] 2025-09-05 ==
* Document Win32-specific AO_NO_ASM_XADD macro in README
* Eliminate 'atomic_thread_fence is unsupported with tsan' gcc-11 warning
* Eliminate 'munmap argument 1 from incompatible pointer type' gcc warning
* Eliminate 'uninitialized memory use' gcc-13 warning in test_atomic
* Fix all broken URLs in comments
* Fix atomic_ops_sysdeps.S compilation for SunPro compiler in CMake script
* Update URLs after repository transfer to bdwgc organization
* Update CMake minimum required version to 3.10
Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
---
.../{libatomic-ops_7.8.2.bb => libatomic-ops_7.8.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/libatomic-ops/{libatomic-ops_7.8.2.bb => libatomic-ops_7.8.4.bb} (89%)
diff --git a/meta/recipes-support/libatomic-ops/libatomic-ops_7.8.2.bb b/meta/recipes-support/libatomic-ops/libatomic-ops_7.8.4.bb
similarity index 89%
rename from meta/recipes-support/libatomic-ops/libatomic-ops_7.8.2.bb
rename to meta/recipes-support/libatomic-ops/libatomic-ops_7.8.4.bb
index 6269133408..d0bb11eb5d 100644
--- a/meta/recipes-support/libatomic-ops/libatomic-ops_7.8.2.bb
+++ b/meta/recipes-support/libatomic-ops/libatomic-ops_7.8.4.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/libatomic_ops-${PV}.tar.gz"
GITHUB_BASE_URI = "https://github.com/bdwgc/libatomic_ops/releases"
-SRC_URI[sha256sum] = "d305207fe207f2b3fb5cb4c019da12b44ce3fcbc593dfd5080d867b1a2419b51"
+SRC_URI[sha256sum] = "2356e002e80ef695875e971d6a4fd8c61ca5c6fa4fd1bf31cce54a269c8bfcd5"
S = "${WORKDIR}/libatomic_ops-${PV}"
next prev parent reply other threads:[~2026-04-09 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 9:29 [scarthgap][PATCH 0/9] scarthgap updates daniel.turull
2026-04-09 9:29 ` [scarthgap][PATCH 1/9] base-passwd: upgrade 3.6.3 -> 3.6.8 daniel.turull
2026-04-09 9:29 ` [scarthgap][PATCH 2/9] gnupg: upgrade 2.4.8 -> 2.4.9 daniel.turull
2026-04-09 9:29 ` [scarthgap][PATCH 3/9] python3-requests: upgrade 2.32.4 -> 2.32.5 daniel.turull
2026-04-09 9:29 ` [scarthgap][PATCH 4/9] bash: upgrade 5.2.21 -> 5.2.37 daniel.turull
2026-04-09 9:29 ` [scarthgap][PATCH 5/9] sudo: upgrade 1.9.17p1 -> 1.9.17p2 daniel.turull
2026-04-09 9:29 ` [scarthgap][PATCH 6/9] lttng-ust: upgrade 2.13.8 -> 2.13.10 daniel.turull
2026-04-09 9:29 ` daniel.turull [this message]
2026-04-09 9:29 ` [scarthgap][PATCH 8/9] liburcu: upgrade 0.14.0 -> 0.14.2 daniel.turull
2026-04-09 9:29 ` [scarthgap][PATCH 9/9] numactl: upgrade 2.0.18 -> 2.0.19 daniel.turull
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=20260409092936.1740143-8-daniel.turull@ericsson.com \
--to=daniel.turull@ericsson.com \
--cc=openembedded-core@lists.openembedded.org \
/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