diff options
| author | Indu Bhagat <indu.bhagat@oracle.com> | 2024-05-23 14:18:23 -0700 |
|---|---|---|
| committer | Indu Bhagat <indu.bhagat@oracle.com> | 2024-07-09 10:23:31 -0700 |
| commit | 6dacff8a2f4d2c24648fb96334fb272b67beff7c (patch) | |
| tree | 784152d0101fe5863fd1c480669a5c81375c203c /gprofng/common/hwcfuncs.c | |
| parent | eb7892c4019bd5d00175c0eb80eb0c5a47a42ca1 (diff) | |
| download | binutils-6dacff8a2f4d2c24648fb96334fb272b67beff7c.zip binutils-6dacff8a2f4d2c24648fb96334fb272b67beff7c.tar.gz binutils-6dacff8a2f4d2c24648fb96334fb272b67beff7c.tar.bz2 | |
doc: sframe: segregate the ABI/arch-specific components
The recipe to interpret the SFrame FRE stack offsets is
ABI/arch-specific.
Although, there is other information in the specification that is
ABI-specific (like pauth_key usage in AArch64), those pieces of
information are now assimmilated in the SFrame specification in a way
that it is fairly difficult to carve then out into a ABI/arch-specific
section without confusing the readers.
For future though, the specification must strive to keep the generic
parts and ABI/arch-specific parts clearly laid out in separate sections.
libsframe/
* doc/sframe-spec.texi: Reorder and adapt the contents.
Diffstat (limited to 'gprofng/common/hwcfuncs.c')
0 files changed, 0 insertions, 0 deletions