public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Bruce Ashfield" <bruce.ashfield@gmail.com>
Cc: <Sundeep.Kokkonda@windriver.com>,
	<Deepesh.Varatharajan@windriver.com>,
	<Randy.MacLeod@windriver.com>, <Hemanth.KumarMD@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] binutils: Upgrade to 2.46 release
Date: Fri, 27 Feb 2026 13:34:29 +0100	[thread overview]
Message-ID: <DGPQXND8Q03F.3UJGBM37U09HA@bootlin.com> (raw)
In-Reply-To: <20260225114339.215291-1-Hemanth.KumarMD@windriver.com>

On Wed Feb 25, 2026 at 12:43 PM CET, Hemanth Kumar M D via lists.openembedded.org wrote:
> From: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
>
> New Features:
> Support for new instructions added to AMD, ARM and RISC-V architectures.
> Support for version 3 of the SFrame standard.
> The readelf program can now display the contents of Global Offset Tables.
> Improved linker tagging support.
>
> Detailed release notes are here [1]
>
> [1] https://lists.gnu.org/archive/html/info-gnu/2026-02/msg00006.html
>

Hi Bruce,

I just want to note that this patch, if merged, will break the xen build
with meta-virt. I believe only the qemuarm64 MACHINE is affected.

ERROR: xen-4.21.0+stable-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/meta-virt/build/build/tmp/work/cortexa57-poky-linux/xen/4.21.0+stable/temp/run.do_compile.2652887' failed with exit code 1
...
| Assembler messages:
| {standard input}:474: Error: unknown or missing system register name at operand 1 -- `msr TEECR32_EL1,x0'
| {standard input}:480: Error: unknown or missing system register name at operand 1 -- `msr TEEHBR32_EL1,x0'
| {standard input}:488: Error: unknown or missing system register name at operand 2 -- `mrs x0,TEECR32_EL1'
| {standard input}:494: Error: unknown or missing system register name at operand 2 -- `mrs x0,TEEHBR32_EL1'

https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/3098

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



           reply	other threads:[~2026-02-27 12:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260225114339.215291-1-Hemanth.KumarMD@windriver.com>]

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=DGPQXND8Q03F.3UJGBM37U09HA@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Deepesh.Varatharajan@windriver.com \
    --cc=Hemanth.KumarMD@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=bruce.ashfield@gmail.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