{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":218332467,"defaultBranch":"main","name":"abi-aa","ownerLogin":"ARM-software","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-10-29T16:25:37.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5690313?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1725532988.0","currentOid":""},"activityList":{"items":[{"before":"a82eef0433556b30539c0d4463768d9feb8cfd0b","after":"aa8733f11076d81889d3c8adcebbcfd833b2030f","ref":"refs/heads/main","pushedAt":"2024-09-23T08:46:34.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"Add sysvabi64 to README","shortMessageHtmlLink":"Add sysvabi64 to README"}},{"before":null,"after":"75ee20778432ce8767e2886b4a7ae7e88fc4af62","ref":"refs/heads/release-links","pushedAt":"2024-09-04T11:18:00.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"slightly tweak the release links generator script\n\n- removed referring to developer.arm.com, as we have moved all the legacy docs\nhere now\n- moved some docs into the 64-bit section","shortMessageHtmlLink":"slightly tweak the release links generator script"}},{"before":"7f13a430efe8e59cb9a4f38043313f5e35f7517e","after":null,"ref":"refs/heads/2024Q3-prep","pushedAt":"2024-09-03T09:30:36.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"}},{"before":"3ec80bdcff012126c0f11cd57daf8e3cb53f91a0","after":"a82eef0433556b30539c0d4463768d9feb8cfd0b","ref":"refs/heads/main","pushedAt":"2024-09-03T09:30:34.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"prepare documents for 2024Q3 release (#279)","shortMessageHtmlLink":"prepare documents for 2024Q3 release (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2501136011\" data-permission-text=\"Title is private\" data-url=\"https://github.com/ARM-software/abi-aa/issues/279\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/ARM-software/abi-aa/pull/279/hovercard\" href=\"https://github.com/ARM-software/abi-aa/pull/279\">#279</a>)"}},{"before":null,"after":"7f13a430efe8e59cb9a4f38043313f5e35f7517e","ref":"refs/heads/2024Q3-prep","pushedAt":"2024-09-02T14:42:14.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"prepare documents for 2024Q3 release","shortMessageHtmlLink":"prepare documents for 2024Q3 release"}},{"before":"0e0a1c54f8065802e3efed0a307294e90ff6aada","after":"3ec80bdcff012126c0f11cd57daf8e3cb53f91a0","ref":"refs/heads/main","pushedAt":"2024-08-30T11:12:22.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"[ATOMICSABI64]: Alpha Draft of Atomics ABI (#256)\n\nThis is the Alpha draft of the C/C++ Atomics Application Binary Interface \r\nStandard for the Arm® 64-bit Architecture\r\n\r\nThis document describes the C/C++ Atomics Application Binary Interface\r\nfor the Arm 64-bit architecture.\r\n\r\nThis document concerns the valid mappings from C/C++ Atomic Operations\r\nto sequences of A64 instructions. This document does not support Armv7.\r\n\r\nFor matters concerning the memory model, please consult §B2 of the Arm\r\nArchitecture Reference Manual.\r\n\r\nWe focus only on a subset of the C11 atomic operations and their mapping\r\nto A64 instructions at the time of writing.\r\n\r\nMore atomics will be added.\r\n\r\nCo-Authored by Wilco Dijkstra (@Wilco1).","shortMessageHtmlLink":"[ATOMICSABI64]: Alpha Draft of Atomics ABI (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2228797566\" data-permission-text=\"Title is private\" data-url=\"https://github.com/ARM-software/abi-aa/issues/256\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/ARM-software/abi-aa/pull/256/hovercard\" href=\"https://github.com/ARM-software/abi-aa/pull/256\">#256</a>)"}},{"before":"201a7cb898c443b6d1c7aa3b8abdaaa55ebf02d8","after":"0e0a1c54f8065802e3efed0a307294e90ff6aada","ref":"refs/heads/main","pushedAt":"2024-08-21T09:23:09.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[aaelf64] Fix PAuthABI relocation details.\n\nThere is a typo in the spelling of R_<CLS_ABS64, it is missing a\nclose angle brackets, and should be R_<CLS>_ABS64.\n\nSimilarly there should only be one entry in the dynamic relocation\ntable, with R_<CLS>_ABS64 retaining the static relocation code but\nusing the dynamic relocation semantics.\n\nAdded a clarifying line to state that the R_<CLS>_ABS64 is both a\nstatic and dynamic relocation.","shortMessageHtmlLink":"[aaelf64] Fix PAuthABI relocation details."}},{"before":"4b25a26b6871a175b111b3dab7eea44cd2106617","after":"201a7cb898c443b6d1c7aa3b8abdaaa55ebf02d8","ref":"refs/heads/main","pushedAt":"2024-08-20T09:59:10.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[aaelf64][pauthabi64] Remove addend in GDAT relocation operation\n\nThe GDAT(S + A) relocation operation requires a static linker to\ncreate a GOT entry for (S + A). Requiring at least one GOT entry\nfor each unique tuple (S, A). Unfortunately no known static linker\nhas implemented this correctly, with one of two forms being\nimplemented instead:\n* GDAT(S) with the addend ignored.\n* GDAT(S) + A with a single GOT entry per S, and A added to the\n  value of GDAT(S).\nThese implementations are correct and consistent only for an\naddend (A) of zero.\n\nNo known compiler uses non-zero addends in relocations that use\nthe GDAT(S+A) operation, although it is possible to generate\nthem using assembly language.\n\nThis change synchronizes the ABI with the behavior of existing\nstatic linker implementations. The benefit of permitting code\ngenerators [*] to use a non zero addend in GDAT(S + A) is judged\nto be lower than implementing GDAT(S + A) correctly in existing\nstatic linkers, many of which assume that there is a single\nGOT entry per unique symbol S.\n\nIt is QoI whether a static linker gives an error if a non zero\naddend is used for a relocation that uses the GDAT(S) operation.\n\nFixes https://github.com/ARM-software/abi-aa/issues/217\nAlso resolves https://github.com/ARM-software/abi-aa/pull/247\n\n[*] The most common use case for a non-zero addend is in\nconstructing a C++ object with a vtable. The first two entries\nin the vtable are the offset to top and a pointer to RTTI, the\nvtable pointer in the object starts at offset 0x10. This offset\ncan be encoded in the relocation addend. We would save an add\ninstruction for each construction of a C++ object with a vtable\nif addends were permitted.","shortMessageHtmlLink":"[aaelf64][pauthabi64] Remove addend in GDAT relocation operation"}},{"before":"c3d0c0be74d71c267bbc35853f4bcbf276a455f1","after":"4b25a26b6871a175b111b3dab7eea44cd2106617","ref":"refs/heads/main","pushedAt":"2024-08-12T12:40:14.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"[NFC] address language suggestions across various documents","shortMessageHtmlLink":"[NFC] address language suggestions across various documents"}},{"before":null,"after":"648df3a589c03756473934ea0a8182cfbb18571d","ref":"refs/heads/lang-fixes","pushedAt":"2024-08-12T10:40:55.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"[NFC] address language suggestions across various documents","shortMessageHtmlLink":"[NFC] address language suggestions across various documents"}},{"before":"1a448ed798d03a4143508580bb8dffc99c188d7d","after":"c3d0c0be74d71c267bbc35853f4bcbf276a455f1","ref":"refs/heads/main","pushedAt":"2024-08-09T15:39:02.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"[AAPCS64] Use oxford comma in soft-float ABI","shortMessageHtmlLink":"[AAPCS64] Use oxford comma in soft-float ABI"}},{"before":"11b87eef9646e5f1629bc82db0c224011ac466ac","after":"1a448ed798d03a4143508580bb8dffc99c188d7d","ref":"refs/heads/main","pushedAt":"2024-07-08T16:11:13.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[AAELF64] Clarify how addends work in MOVZ, MOVK and ADRP.\n\nThis brings AAELF64 into line with AAELF32, which already has a\nsimilar clarification for the MOVW+MOVT pair. For the instructions\nwhich shift their operand left (ADRP, and the shifted MOVZ and MOVK),\nif the relocation addend is taken from the input value of the\nimmediate field, it is not treated as shifted.\n\nThe rationale is that this allows a sequence of related instructions\nto consistently compute the same value (symbol + small offset), and\ncooperate to load that value into the target register, one small chunk\nat a time. For example, this would load `mySymbol + 0x123`:\n\n  mov  x0, #0x123          ; R_AARCH64_MOVW_UABS_G0_NC(mySymbol)\n  movk x0, #0x123, lsl #16 ; R_AARCH64_MOVW_UABS_G1_NC(mySymbol)\n  movk x0, #0x123, lsl #32 ; R_AARCH64_MOVW_UABS_G2_NC(mySymbol)\n  movk x0, #0x123, lsl #48 ; R_AARCH64_MOVW_UABS_G3(mySymbol)\n\nThe existing text made it unclear whether the addends were shifted or\nnot. If they are interpreted as shifted, then nothing useful happens,\nbecause the first instruction would load the low 16 bits of\n`mySymbol+0x123`, and the second would load the next 16 bits of\n`mySymbol+0x1230000`, and so on. This doesn't reliably get you _any_\nuseful offset from the symbol, because the relocations are processed\nindependently, so that a carry out of the low 16 bits won't be taken\ninto account in the next 16.\n\nIf you do need to compute a large offset from the symbol, you have no\noption but to use SHT_RELA and specify a full 64-bit addend: there's\nno way to represent that in an SHT_REL setup. But interpreting the\nSHT_REL addends in the way specified here, you can at least specify\n_small_ addends successfully.","shortMessageHtmlLink":"[AAELF64] Clarify how addends work in MOVZ, MOVK and ADRP."}},{"before":"f14c8ffc67360d4da822d99555c8f83f879a9128","after":"11b87eef9646e5f1629bc82db0c224011ac466ac","ref":"refs/heads/main","pushedAt":"2024-07-08T13:16:13.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[aapcs64] Round up to a multiple of 8, not just to 8","shortMessageHtmlLink":"[aapcs64] Round up to a multiple of 8, not just to 8"}},{"before":"01f97f3dcba1640e7291d09ecb5ec71216f906b1","after":"f14c8ffc67360d4da822d99555c8f83f879a9128","ref":"refs/heads/main","pushedAt":"2024-07-02T15:23:57.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[PAUTHABIELF64] Add R_AARCH64_AUTH_GOT_ADR_PREL_LO21 relocation\n\nWith the tiny code model and a signed GOT, an adr instruction is\nneeded to get the address of the GOT entry for input to the\nauthenication. For example:\n\nadr x8, :got_auth: symbol\nldr x0, [x8]\n// Authenticate to get unsigned pointer\nautia x0, x8\n\nThe adr requires a new relocation code where there isn't a direct\nequivalent in the main ABI as there is not need to take the\naddress of the GOT slot when no authentication is required.\n\nWe define R_AARCH64_AUTH_GOT_ADR_PREL21_LO21 for this purpose\nfollowing the naming convention of R_<CLS>_ADR_PREL_LO21. which is\nits closest equivalent.","shortMessageHtmlLink":"[PAUTHABIELF64] Add R_AARCH64_AUTH_GOT_ADR_PREL_LO21 relocation"}},{"before":"29f4a4d764bbda1cf00f9d95d387677c38a08a45","after":"01f97f3dcba1640e7291d09ecb5ec71216f906b1","ref":"refs/heads/main","pushedAt":"2024-07-02T14:43:09.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[pauthabi64] Add note for RAARCH64_AUTH_GOT_ADD_LO12_NC\n\nThere is no equivalent for this relocation in the standard ABI\nit is used by runtime code to calculate the address of\na GOT slot so it can be used as one of the inputs to an\nauthenticate instruction. Add a note that this matches up\nwith the :got_auth_lo12: operator for future reference.\n\nPart of https://github.com/ARM-software/abi-aa/issues/253","shortMessageHtmlLink":"[pauthabi64] Add note for RAARCH64_AUTH_GOT_ADD_LO12_NC"}},{"before":"99d4311dc3c1eb0e0850b1f2396af942ba008cce","after":"29f4a4d764bbda1cf00f9d95d387677c38a08a45","ref":"refs/heads/main","pushedAt":"2024-07-02T14:40:24.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[PAUTHABIELF64] Remove alternative ELF marking scheme\n\nNo implementation is using the alternative marking scheme; take\nthe opportunity to remove it, so that toolchains do not need to\nsupport it.\n\nThe alternative marking scheme started as the default one back\nwhen the spec was written. At the time there were only prototype\nimplementations for which signing schema compatibility and\nversioning weren't important.\n\nOver time Arm's ELF marking for SysV has evolved such that the\npreference for ELF executables and shared-libraries is to use\nGNU Program Properties. We intend to migrate to Build Attributes\nfor relocatable objects, but until that change is made GNU\nProgram Properties should be used in relocatable objects too.\n\nThe alternative ELF marking scheme was preserved for backwards\ncompatibility, however no current implementation needs that so\nit can be removed.","shortMessageHtmlLink":"[PAUTHABIELF64] Remove alternative ELF marking scheme"}},{"before":"5c0a393f50e083ccca9f32ca94995211141fe858","after":"99d4311dc3c1eb0e0850b1f2396af942ba008cce","ref":"refs/heads/main","pushedAt":"2024-06-18T08:47:59.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"rsandifo-arm","name":null,"path":"/rsandifo-arm","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28043039?s=80&v=4"},"commit":{"message":"[aapcs64] Clarify meaning of \"it\" when preserving z and p regs\n\nAt least one community got confused as to whether it refered\nto the callee or the caller. Use subroutine instead of it to\nmake it clear that we are referring to the same subroutine\nthat takes z and p registers as arguments.\n\nFixes https://github.com/ARM-software/abi-aa/issues/266","shortMessageHtmlLink":"[aapcs64] Clarify meaning of \"it\" when preserving z and p regs"}},{"before":"d4af6f2559a6df93a5567fee616b6b86e7efd4df","after":"5c0a393f50e083ccca9f32ca94995211141fe858","ref":"refs/heads/main","pushedAt":"2024-05-29T08:46:55.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"rsandifo-arm","name":null,"path":"/rsandifo-arm","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28043039?s=80&v=4"},"commit":{"message":"Updated the change history table in aapcs64.rst.","shortMessageHtmlLink":"Updated the change history table in aapcs64.rst."}},{"before":"7c2fbbd6d32c906c709804f873b67308d1ab46e2","after":"d4af6f2559a6df93a5567fee616b6b86e7efd4df","ref":"refs/heads/main","pushedAt":"2024-05-07T13:35:11.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"Fix the typo in Operation Definition for R_ARM_REL32\n\nR_ARM_REL32 relocation's operation is defined as ((S + A) | T) – P but an extra \"|\" is left in the current version.","shortMessageHtmlLink":"Fix the typo in Operation Definition for R_ARM_REL32"}},{"before":"38f76253ddea9996442e3e768af0661a7b042ff1","after":"7c2fbbd6d32c906c709804f873b67308d1ab46e2","ref":"refs/heads/main","pushedAt":"2024-03-22T11:49:51.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[CLIBABI32] Restore missing reference to EDOM.\n\nI just noticed a paragraph that was grammatically confusing because it\ncontained a comma with no word before it, and an equality with no\nleft-hand side.\n\nIt looks to me as if the <errno.h> macro name EDOM was accidentally\ndeleted in both cases. (Rationale: EDOM is an error code closely\nrelated to ERANGE, and matches the claim in the paragraph that its\nconsensus value is 33 – that's its value on Linux, for example.)\n\nSearching for ERANGE in the rest of the document turned up another two\nplaces where there was a missing word that looked as if it ought to be\n\"EDOM\".\n\nI've no idea how this happened! But it seems like an easy fix.","shortMessageHtmlLink":"[CLIBABI32] Restore missing reference to EDOM."}},{"before":"0233ab145b8f13cc808ac86b81c4c9188a64c112","after":"38f76253ddea9996442e3e768af0661a7b042ff1","ref":"refs/heads/main","pushedAt":"2024-03-18T11:31:53.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[AAELF64][PAUTHABI64] Assign PAuthABI relocation codes.\n\nNow that there will be a concrete implementation of PAuthABI in upstream\nLLVM we need to move the PAuthABI relocation codes out of the space\nreserved for private experiments to their final codes. These are in\nthe range of codes already reserved for the PAuthABI in AAELF64.\n\nThe description of the operations will remain in the PAuthABI64 as\nthis remains an extension.","shortMessageHtmlLink":"[AAELF64][PAUTHABI64] Assign PAuthABI relocation codes."}},{"before":"8d5e422ed087f0d81c94b2356838e00ea106b57c","after":"0233ab145b8f13cc808ac86b81c4c9188a64c112","ref":"refs/heads/main","pushedAt":"2024-03-15T17:15:28.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[SYSVABI64] Reserve dynamic tags used by memtagabielf64 and pauthabi64\n\nThe alpha ELF extension documents define dynamic tags. To avoid\navoidable clashes with the main specification, mark the values\nused as reserved.","shortMessageHtmlLink":"[SYSVABI64] Reserve dynamic tags used by memtagabielf64 and pauthabi64"}},{"before":"879df44cb00de276a74034180adf61996b03afda","after":"8d5e422ed087f0d81c94b2356838e00ea106b57c","ref":"refs/heads/main","pushedAt":"2024-03-15T16:34:19.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"[PAuthABIELF64] Use .note.gnu.property section as ELF marking scheme.\n\nMake the alternative .note.gnu.property section the default ELF\nmarking scheme for ELF executables and shared libraries. Preserve\nthe original SHT_NOTE section as an alternative for legacy\ncompatibility.\n\nExtract the common parts of all of the ELF marking schemes\ninto \"Core Information\". The ELF marking schemes now describe\nhow they encode the \"Core Information\". The compatibility model\nis now written in terms of the \"Core Information\".\n\nThe default PAuth vendor and version for ELF files with no ELF\nmarking is (0,0) which is incompatible with everything. This is\nthe safest default as there is no information about what, if any,\nsigning schema is used by that ELF file.\n\nImplementations can change this default in the presence of\nsupplemental information, such as a linker command line option.\nFor example there could be the equivalent of the -z force-bti\nwhich declares that all ELF objects without the BTI property are\nconsidered to be compatible.","shortMessageHtmlLink":"[PAuthABIELF64] Use .note.gnu.property section as ELF marking scheme."}},{"before":"c8b9225e0207d61dadbd05cd5eabf737e4ef77d4","after":"879df44cb00de276a74034180adf61996b03afda","ref":"refs/heads/main","pushedAt":"2024-03-07T12:05:08.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"fixup! [aadwarf64] Add DWARF support for unwinding with FEAT_PAuth_LR enabled","shortMessageHtmlLink":"fixup! [aadwarf64] Add DWARF support for unwinding with FEAT_PAuth_LR…"}},{"before":"c87dc3acda429fa412ea5952bd00725b6e11b11c","after":"c8b9225e0207d61dadbd05cd5eabf737e4ef77d4","ref":"refs/heads/main","pushedAt":"2024-03-05T16:32:18.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"Fix aadwarf64 typo in readme","shortMessageHtmlLink":"Fix aadwarf64 typo in readme"}},{"before":"5b9c1454da7342fdf2b1f71d8a3d68dfe9a1de2b","after":"c87dc3acda429fa412ea5952bd00725b6e11b11c","ref":"refs/heads/main","pushedAt":"2024-02-19T13:32:28.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"Clarify R_<CLS>_RELATIVE optimization wording\n\nThe optimization is applied by the static linker, so we should reword\nthe sentence from that perspective. Thanks to @smithp35 for suggesting\nthe wording.","shortMessageHtmlLink":"Clarify R_&lt;CLS&gt;_RELATIVE optimization wording"}},{"before":"decf60407ccb4fd9934cd07f86537414b71903e1","after":"5b9c1454da7342fdf2b1f71d8a3d68dfe9a1de2b","ref":"refs/heads/main","pushedAt":"2024-02-07T10:13:01.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"Define soft-float PCS for AArch64\n\nWith the release of the Cortex-R82, we now have an AArch64 CPU which can\nbe built without any floating-point instructions or registers, so I\nthink we should re-consider our decision to not have a soft-float\nvariant of the AArch64 PCS.\n\nI've worded this as a variant over the base PCS, to keep it simple.\n\nNo compiler implements this yet, but clang does already allow passing\nfloating-point types without an FPU, and seems to implement the first\nbullet point correctly. I'm working on LLVM patches which will\nimplement bullet points 2 and 3.\n\nGCC doesn't currently allow any use of floating-point types without an\nFPU for AArch64, so we don't need to worry about compatibility with\nexisting code there.\n\nFor the fourth bullet point, I don't think we need to define the PCS for\nvector types, because these are only defined by the ACLE when the\nrelevant hardware exists.","shortMessageHtmlLink":"Define soft-float PCS for AArch64"}},{"before":"fe46d4335d87e792991ceab9c8fd7b79f927a918","after":"decf60407ccb4fd9934cd07f86537414b71903e1","ref":"refs/heads/main","pushedAt":"2024-02-05T15:33:54.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"Promote the SME(2) ABI status from Alpha to Beta\n\nThe SME and SME2 ABI have been implemented in upstream GCC and\nClang/LLVM, so I think they're ready to be treated as Beta.","shortMessageHtmlLink":"Promote the SME(2) ABI status from Alpha to Beta"}},{"before":"cc782c4896e5c3ce72947f9e120d783386275d75","after":"fe46d4335d87e792991ceab9c8fd7b79f927a918","ref":"refs/heads/main","pushedAt":"2024-02-05T10:50:14.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"stuij","name":"Ties Stuij","path":"/stuij","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/192309?s=80&v=4"},"commit":{"message":"Fix 'unit32' typo in addenda32.rst\n\nShould be 'uint32'.","shortMessageHtmlLink":"Fix 'unit32' typo in addenda32.rst"}},{"before":"b0f1111afbd7d0aa8f2b160dd63971e69c99955a","after":"cc782c4896e5c3ce72947f9e120d783386275d75","ref":"refs/heads/main","pushedAt":"2024-01-31T15:20:53.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"smithp35","name":"Peter Smith","path":"/smithp35","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/45786696?s=80&v=4"},"commit":{"message":"Fix \"reloction\" typo\n\nIt should say \"relocation\".","shortMessageHtmlLink":"Fix \"reloction\" typo"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yM1QwODo0NjozNC4wMDAwMDBazwAAAAS9uUFE","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yM1QwODo0NjozNC4wMDAwMDBazwAAAAS9uUFE","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wMS0zMVQxNToyMDo1My4wMDAwMDBazwAAAAPuLgph"}},"title":"Activity · ARM-software/abi-aa"}