Skip to content

Conversation

@dcbaker
Copy link
Member

@dcbaker dcbaker commented Dec 9, 2025

We need to ensure that we have detailed information on the machine we're targeting. This was previously done by creating an ad hoc info struct, but now we get it from the Environment. This can be a problem if NASM (or MASM, or litearasm) are instantiated before a C compiler, since the information isn't the detailed version yet.

This fixes that by updating the machine info instead.

Fixes: #15361

@dcbaker dcbaker requested a review from jpakkane as a code owner December 9, 2025 19:38
@dcbaker dcbaker added this to the 1.10.1 milestone Dec 9, 2025
@dcbaker dcbaker force-pushed the submit/detect-machine-info-for-asm branch from 6dd64eb to b25e5f0 Compare December 9, 2025 19:39
Instead of having it in the interpreter. We're going to need to update
this inside of the compiler detection in the next patch.
The ASM compilers need the machine information to be up to date before
they're initialized. Which is a reasonable thing as they use the c
linker information. This was done by creating a unique MachineInfo. That
code was dropped when the compilers were refactored to use the
Environment instead of a separate MachineInfo.

This patch is honestly not what I'd hope for, but it's minimal for
application to the stable branch. This should be followed up by more
cleanups, but that will involve more work.

Fixes: mesonbuild#15361
@dcbaker dcbaker force-pushed the submit/detect-machine-info-for-asm branch from b25e5f0 to 08bf58d Compare December 10, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1.10 regression: Rewriter fails if nasm is enabled

1 participant