[AArch64] Add support for SHF_AARCH64_PURECODE ELF section flag (1/3) by Il-Capitano · Pull Request #125687 · llvm/llvm-project (original) (raw)
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
Add support for the new SHF_AARCH64_PURECODE ELF section flag: ARM-software/abi-aa#304
The general implementation follows the existing one for ARM targets.
Generating object files with the SHF_AARCH64_PURECODE
flag set is
enabled by the +execute-only
target feature.
This was referenced
Feb 4, 2025
joaosaffran pushed a commit to joaosaffran/llvm-project that referenced this pull request
Add support for the new SHF_AARCH64_PURECODE ELF section flag: ARM-software/abi-aa#304
The general implementation follows the existing one for ARM targets.
Generating object files with the SHF_AARCH64_PURECODE
flag set is
enabled by the +execute-only
target feature.
Related PRs:
- Clang: llvm#125688
- LLD: llvm#125689
MaskRay pushed a commit that referenced this pull request
…flag (3/3) (#125689)
Add support for the new SHF_AARCH64_PURECODE ELF section flag: ARM-software/abi-aa#304
The general implementation follows the existing one for ARM targets. The
output section only has the SHF_AARCH64_PURECODE
flag set if all input
sections have it set.
Related PRs:
llvm-sync bot pushed a commit to arm/arm-toolchain that referenced this pull request
…LF section flag (3/3) (#125689)
Add support for the new SHF_AARCH64_PURECODE ELF section flag: ARM-software/abi-aa#304
The general implementation follows the existing one for ARM targets. The
output section only has the SHF_AARCH64_PURECODE
flag set if all input
sections have it set.
Related PRs:
- LLVM: llvm/llvm-project#125687
- Clang: llvm/llvm-project#125688
sivan-shani pushed a commit to sivan-shani/llvm-project that referenced this pull request
Add support for the new SHF_AARCH64_PURECODE ELF section flag: ARM-software/abi-aa#304
The general implementation follows the existing one for ARM targets.
Generating object files with the SHF_AARCH64_PURECODE
flag set is
enabled by the +execute-only
target feature.
Related PRs:
- Clang: llvm#125688
- LLD: llvm#125689
davemgreen pushed a commit that referenced this pull request
…g (2/3) (#125688)
Add support for the new SHF_AARCH64_PURECODE ELF section flag: ARM-software/abi-aa#304
The general implementation follows the existing one for ARM targets.
Simlarly to ARM targets, generating object files with the
SHF_AARCH64_PURECODE
flag set is enabled by the
-mexecute-only
/-mpure-code
driver flag.
Related PRs:
llvm-sync bot pushed a commit to arm/arm-toolchain that referenced this pull request
…section flag (2/3) (#125688)
Add support for the new SHF_AARCH64_PURECODE ELF section flag: ARM-software/abi-aa#304
The general implementation follows the existing one for ARM targets.
Simlarly to ARM targets, generating object files with the
SHF_AARCH64_PURECODE
flag set is enabled by the
-mexecute-only
/-mpure-code
driver flag.
Related PRs:
- LLVM: llvm/llvm-project#125687
- LLD: llvm/llvm-project#125689
Il-Capitano added a commit to Il-Capitano/llvm-project that referenced this pull request
Support for execute-only code generation (llvm#125687) introduced a bug in the case where the memtag sanitizer is used in a module containing a mix of execute-only and non-execute-only functions.
The bug is caused by using return
instead of break
to short-circuit
a loop, which meant that the rest of the function dealing with memtag
sanitizer logic wasn't run.
Il-Capitano added a commit that referenced this pull request
Support for execute-only code generation (#125687) introduced a bug in the case where the memtag sanitizer is used in a module containing a mix of execute-only and non-execute-only functions.
The bug is caused by using return
instead of break
to short-circuit
a loop, which meant that the rest of the function dealing with memtag
sanitizer logic wasn't run.
Ankur-0429 pushed a commit to Ankur-0429/llvm-project that referenced this pull request
Support for execute-only code generation (llvm#125687) introduced a bug in the case where the memtag sanitizer is used in a module containing a mix of execute-only and non-execute-only functions.
The bug is caused by using return
instead of break
to short-circuit
a loop, which meant that the rest of the function dealing with memtag
sanitizer logic wasn't run.