From Fedora Project Wiki
(Created page with "== ABI variants == Some architectures have binary-incompatible sub-architecture variants. Historic examples are non-executable stacks (handled with the <code>GNU_STACK</code...") |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
Some architectures have binary-incompatible sub-architecture variants. Historic examples are non-executable stacks (handled with the <code>GNU_STACK</code> program header and the <code>.note.GNU-stack</code> section) and 16-byte stack alignment on i386 (which did not receive any markup). | Some architectures have binary-incompatible sub-architecture variants. Historic examples are non-executable stacks (handled with the <code>GNU_STACK</code> program header and the <code>.note.GNU-stack</code> section) and 16-byte stack alignment on i386 (which did not receive any markup). | ||
Potential | Potential such changes are: | ||
* [https://gcc.gnu.org/wiki/Ieee128PowerPC The format of <code>long double</code> on POWER] | * [https://gcc.gnu.org/wiki/Ieee128PowerPC The format of <code>long double</code> on POWER] | ||
MIPS executables already have a PT_ABIFLAGS segment, as well as PT_REGINFO. | |||
[[Category:Toolchain/Watermark/Provisional]] | [[Category:Toolchain/Watermark/Provisional]] | ||
Latest revision as of 16:37, 27 September 2017
ABI variants
Some architectures have binary-incompatible sub-architecture variants. Historic examples are non-executable stacks (handled with the GNU_STACK program header and the .note.GNU-stack section) and 16-byte stack alignment on i386 (which did not receive any markup).
Potential such changes are:
MIPS executables already have a PT_ABIFLAGS segment, as well as PT_REGINFO.