Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] nasm: upgrade 3.01 -> 3.02
Date: Wed, 08 Jul 2026 14:11:54 +0200	[thread overview]
Message-ID: <DJT6HQ4N7EGR.2UDG8J0QL9AL4@bootlin.com> (raw)
In-Reply-To: <20260706135009.1818867-1-ross.burton@arm.com>

On Mon Jul 6, 2026 at 3:50 PM CEST, Ross Burton via lists.openembedded.org wrote:
> Drop the backported C23 patch, and replace the debug-prefix-map patches
> with backports that are now merged upstream (thanks Joshua Watt).
>
> Out-of-tree builds work again, so switch back to autotools.
>
> Upstream release notes:
> - Fix build problems on C23 compilers using a pre-C23 version of <stdbool.h>.
> - The immediate form of the JMPE instruction (opcode 0F B8) has been
>   changed to an absolute address.
> - Various build fixes.
> - Corrections to assembling encodings.
> - Corrections to disassembling.
> - Whole bunch of minor fixes to operand sizes, operand size prefixes.
> - Add support for C2y-style \o escape sequences, braced escape
>   sequences, and as NASM extensions, decimal escape sequences (\d) and
>   control-character escape sequences (\^).
> - Fix generation of the short opcodes for ADD, OR, ADC, SBB, AND, SUB,
>   XOR, and CMP AL,imm8.
> - Fix truncation of the generated constant to 63 bits when invoking a
>   single-line macro when an argument is defined as =/b or =/ub.
> - Add an %env() preprocessor function as a more robust and flexible
>   alternative to the %! construct.
> - The maximum number of multi-line macro parameters is now a
>   configurable limit.
> - The --limi- options and %pragma limit now accept the keywords
>   default, maximum, and reset.
> - Fix parsing of seg:offs–style FAR pointers in EQU.
> - Fix the %clear preprocessor directive hanging when given parameters.
> - Fix a crash when -M directives were used in response files.
> - New listing option -Lc to include the contents of INCBIN files.
> - New listing option -Lt to include the output from every iteration of
>   TIMES and ALIGN directives.
> - The %pragma list options directive now support resetting options to
>   their command-line default.
> - New predefined macros __?LIST_OPTIONS?__ and
>   __?LIST_OPTIONS_DEFAULT?__ to query the active and command-line
>   default listing options.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---

Hi Ross,

Sorry but it looks like this upgrade is breaking the reproducibility
test for ffmpeg:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/4343
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260707-b241bpry/

It looks like libav built code differs. Can you have a look at this?

Thanks,
Mathieu

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



  reply	other threads:[~2026-07-08 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 13:50 [PATCH] nasm: upgrade 3.01 -> 3.02 Ross Burton
2026-07-08 12:11 ` Mathieu Dubois-Briand [this message]
2026-07-10 11:01   ` [OE-core] " Alexander Kanavin
2026-07-10 14:00     ` Joshua Watt

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=DJT6HQ4N7EGR.2UDG8J0QL9AL4@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.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