diff options
| author | Jens Remus <jremus@linux.ibm.com> | 2024-07-04 10:34:12 +0200 |
|---|---|---|
| committer | Jens Remus <jremus@linux.ibm.com> | 2024-07-04 10:34:12 +0200 |
| commit | 8086fe0b3dea767f56cd1f1bf2e78fb427c508e0 (patch) | |
| tree | 30da04d5fa4cd421a97024ff3edeb1ad010baa9b /gprofng/src | |
| parent | 73b56ef2fda3cab2cc1da7e4ee3cb86453a21aa8 (diff) | |
| download | binutils-8086fe0b3dea767f56cd1f1bf2e78fb427c508e0.zip binutils-8086fe0b3dea767f56cd1f1bf2e78fb427c508e0.tar.gz binutils-8086fe0b3dea767f56cd1f1bf2e78fb427c508e0.tar.bz2 | |
gas: Enhance arch-specific SFrame configuration descriptions
Explicitly mention "SFrame" in the descriptions for the architecture-
specific SFrame configuration macros, variables, and functions.
Use the term "frame pointer" (FP) instead of "base pointer". This aligns
with the terminology used in the SFrame specification. Additionally it
helps not to confuse "base-pointer register" with the term "BASE_REG"
used in the specification to denote either the SP or FP register.
Specify what the SFRAME_CFA_*_REG register numbers are used for:
- SP (stack pointer): CFA tracking
- FP (frame pointer): CFA and FP tracking
- RA (return address): RA tracking
Align the descriptions for definitions in the source files to the
declarations in the header files.
gas/
* config/tc-aarch64.h: Enhance architecture-specific SFrame
configuration descriptions.
* config/tc-aarch64.c: Likewise.
* config/tc-i386.h: Likewise.
* config/tc-i386.c: Likewise.
Signed-off-by: Jens Remus <jremus@linux.ibm.com>
Diffstat (limited to 'gprofng/src')
0 files changed, 0 insertions, 0 deletions