Skip to content

[snippy] Propagate mabi to target machine#408

Open
MaxGud10 wants to merge 1 commit intosyntacore:mainfrom
MaxGud10:fix-mabi-abi-in-elf
Open

[snippy] Propagate mabi to target machine#408
MaxGud10 wants to merge 1 commit intosyntacore:mainfrom
MaxGud10:fix-mabi-abi-in-elf

Conversation

@MaxGud10
Copy link
Copy Markdown
Contributor

Fixes #20

Previously, mabi was stored in the configuration and emitted as a module flag,
but it was not propagated to TargetMachine creation.

As a result, the generated ELF ABI did not always match the requested mabi
unless the corresponding floating-point features were also forced through
mattr.

This change passes mabi through TargetOptions::MCOptions.ABIName when
creating the target machine and adds a regression test that checks the ELF
header flags for lp64d.

@MaxGud10 MaxGud10 changed the title [llvm-snippy] Propagate mabi to target machine [snippy] Propagate mabi to target machine Mar 19, 2026
@MaxGud10 MaxGud10 force-pushed the fix-mabi-abi-in-elf branch from 8ca956e to 5863e94 Compare March 19, 2026 16:09
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.

Looks like mabi option doesn't affect ABI of generated ELF

1 participant