Merge branch 'ARM-software:main' into btilinker

.github/workflows/ci.yml

@@ -7,9 +7,9 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v4
     - name: setup python
-      uses: actions/setup-python@v2
+      uses: actions/setup-python@v5
       with:
         python-version: '3.x'
     - name: install packages
@@ -18,7 +18,7 @@ jobs:
       run: tools/common/check-rst-syntax.sh
     - name: build PDFs
       run: tools/rst2pdf/generate-pdfs.sh PDFs
-    - uses: actions/upload-artifact@v2
+    - uses: actions/upload-artifact@v4
       with:
         name: PDFs
         path: PDFs

CONTRIBUTING.md

@@ -43,6 +43,41 @@ changes.
 If you want to make ABI changes that for some reason can't be discussed in
 public, you can send an email to [email protected].
 
+### Extension documents
+While the majority of new proposals can be added to existing
+documents. Proposals that extend the ABI, but are not yet stable are
+placed in an extension document. An example of an extension document
+is the PAuth Extension to ELF for Arm 64-bit Architecture. Extension
+documents have the following requirements:
+
+1. The document status must be Alpha.
+2. The document has an owner recorded in the table below. The owner
+   need not be from Arm.
+3. The document must not clash with other ABI extension documents, or
+   both extensions must be marked as being incompatible.
+
+
+The Arm approval process for accepting the extension is as follows:
+
+1. At least one person within Arm has reviewed and accepted the pull
+   request.
+2. There is a consensus within Arm that the extension can be added to
+   the ABI.
+
+Extension documents can move into the main ABI when the following conditions hold:
+
+1. The information in the document is stable.
+2. There is an implementation of the extension.
+3. The boundaries of when the extension applies are clear.
+
+An extension document that moves into the main ABI will add the
+necessary information to the main documents. In addition any design
+and rationale in the extension document will be moved to a new
+document in the design-documents folder.
+
+When the extension has either moved into the main ABI or has been
+withdrawn it will be moved to an archive folder.
+
 ## Manual checking of the PDF documents and Continuous Integration
 
 To check the outcome of your changes, run the `tools/rst2pdf/generate-pdfs.sh`

README.md

@@ -72,6 +72,7 @@ DWARF for the Arm 64-bit Architecture                              | [aadwarf64]
 C++ ABI for the Arm 64-bit Architecture                            | [cppabi64](cppabi64/cppabi64.rst)    | [2020Q2](legacy-documents/cppabi64/ihi0059_E/IHI0059E_2020Q2_cppabi64.pdf)
 Vector Function ABI for the Arm 64-bit Architecture                | [vfabia64](vfabia64/vfabia64.rst)    | [2019Q2](legacy-documents/vfabia64/101129_1920/101129_1920_01_en.pdf)
 C/C++ Atomics ABI for the Arm 64-bit Architecture                  | [atomicsabi64](atomicsabi64/atomicsabi64.rst)    | n/a
+System V ABI for the Arm 64-bit Architecture                       | [sysvabi64](sysvabi64/sysvabi64.rst) | n/a
 
 
 ### ABI for the Arm 64-bit Architecture with SVE support