)]}'
{
  "commit": "fe4a952931334dee80378c9f0606745976d8b30f",
  "tree": "36342a13ff998c3129d966e3575b9702f02ab5c6",
  "parents": [
    "b8ac7ad17b0299d91976fed3e660809225556b2b"
  ],
  "author": {
    "name": "Matthieu Longo",
    "email": "matthieu.longo@arm.com",
    "time": "Fri Sep 12 17:26:38 2025 +0100"
  },
  "committer": {
    "name": "Matthieu Longo",
    "email": "matthieu.longo@arm.com",
    "time": "Fri Mar 06 10:33:21 2026 +0000"
  },
  "message": "ld: clarify comments on /DISCARD/ output section behavior\n\nThe previous comments made it difficult to understand how the /DISCARD/\noutput section interacts with non-contiguous regions.\n\nIn summary, the general rule is that the first (top-most) clause takes\nprecedence over subsequent ones:\n- If /DISCARD/ appears first, the section is dropped. There is no need\n  to warn about potential behavior changes with non-contiguous regions\n  when the section is already discarded.\n- If /DISCARD/ follows clauses that assign the input section to an output\n  section, /DISCARD/ is ignored. If the input section can\u0027t be assigned\n  to the output section for a later reason, an error will be raised.\n  Otherwise the input section will be assigned as intended to an output\n  section specified by one of the matching clauses previous to /DISCARD/.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bc008c59df1fc703643635f627a0d0f0e6b01c5a",
      "old_mode": 33188,
      "old_path": "ld/ldlang.c",
      "new_id": "656edeb4981442cf3eb7f93bdbfaff323dbbecc7",
      "new_mode": 33188,
      "new_path": "ld/ldlang.c"
    },
    {
      "type": "modify",
      "old_id": "730599ef289d4bfa2911498515a4671cb20fb6f4",
      "old_mode": 33188,
      "old_path": "ld/testsuite/ld-aarch64/non-contiguous-mem/non-contiguous-ok-5.warn",
      "new_id": "7cf8af73a567c7d447687f072acdb743848e2eae",
      "new_mode": 33188,
      "new_path": "ld/testsuite/ld-aarch64/non-contiguous-mem/non-contiguous-ok-5.warn"
    }
  ]
}