Skip to content

Commit

Permalink
[buildattr64] Recommend aeabi_pauthabi is only emitted when needed
Browse files Browse the repository at this point in the history
The aeabi_pauthabi subsection is mandatory, which means that if it
is present an object consumer is required to understand the contents
of the subsection. That makes a relocatable object containing
an aeabi_pauthabi subsection with explicit 0 values for the tags
less portable than relying on the implicit 0 values when the
subsection isn't present.
  • Loading branch information
smithp35 committed Dec 10, 2024
1 parent e61bc69 commit ada00cc
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions buildattr64/buildattr64.rst
Original file line number Diff line number Diff line change
Expand Up @@ -222,6 +222,8 @@ changes to the content of the document for that release.
| | | Clarify that the same attribute with different values is an error. |
| | | Rename subsection names to avoid - character which can be difficult |
| | | for assemblers to parse as a single token. |
| | | Recommend that aeabi_pauthabi subsection not emitted when pauthabi |
| | | not used. |
+------------+---------------------+---------------------------------------------------------------------+

References
Expand Down Expand Up @@ -940,6 +942,11 @@ While the requirement for the ``FEAT_PAuth`` extension is recorded in
the architectural features. The signing schema is software defined
with more complex compatibility requirements.

Relocatable objects not using the PAuthABI are recommended not to
output the "aeabi_pauthabi" subsection with explicit values of 0 for
the tags. This permits a relocatable object to be used by an object
consumer that does not implement the "aeabi_pauthabi" subsection.

header contents
^^^^^^^^^^^^^^^

Expand Down

0 comments on commit ada00cc

Please sign in to comment.