From: Hemanth.KumarMD@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: Sundeep.Kokkonda@windriver.com, Hemanth.KumarMD@windriver.com,
sowmyasathram12@gmail.com
Subject: [wrynose][PATCH] binutils: stable 2.46 branch updates
Date: Tue, 18 Aug 2026 23:57:48 -0700 [thread overview]
Message-ID: <20260819065748.492293-1-Hemanth.KumarMD@windriver.com> (raw)
From: Sowmya Sathram <sowmyasathram12@gmail.com>
Below commits from the binutils-2.46 stable branch are updated
on top of the 2.46.1 release.
046eeeef472 x86: Check XMM destination when optimizing 128-bit VPBROADCASTQ
2c77fbc7007 PR 34204 dlltool SEGVs with --exclude-symbols
38093d82a3e Re-enable development on the 2.46 branch
Test Results:
Before After Diff
No. of expected passes 327 327 0
No. of untested testcases 5 5 0
No. of unsupported tests 9 9 0
Signed-off-by: Sowmya Sathram <sowmyasathram12@gmail.com>
Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
---
meta/recipes-devtools/binutils/binutils-2.46.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/binutils/binutils-2.46.inc b/meta/recipes-devtools/binutils/binutils-2.46.inc
index cab270cea5..b00d2bb069 100644
--- a/meta/recipes-devtools/binutils/binutils-2.46.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.46.inc
@@ -23,7 +23,7 @@ CVE_STATUS[CVE-2025-69651] = "disputed: observed behavior only in pre-release co
CVE_STATUS[CVE-2025-69649] = "fixed-version: Fixed from version 2.46"
CVE_STATUS[CVE-2025-69652] = "fixed-version: Fixed from version 2.46"
-SRCREV ?= "5e56594815854de5eca35c7c04b11705d0f19c02"
+SRCREV ?= "a9c090db342ac76f10bc47258ef8e58f7eaca748"
BINUTILS_GIT_URI ?= "git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=https"
SRC_URI = "\
${BINUTILS_GIT_URI} \
--
2.49.0
reply other threads:[~2026-08-19 6:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260819065748.492293-1-Hemanth.KumarMD@windriver.com \
--to=hemanth.kumarmd@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sowmyasathram12@gmail.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