)]}'
{
  "commit": "45f65dd9485418fd371d5e60b698b873bf555ef3",
  "tree": "9e2f3900d134b7dad01bcae651f9a97fc284de22",
  "parents": [
    "0173df4cc5e05fd460822ef3ae5f8ab9e5879bb7"
  ],
  "author": {
    "name": "Antoni Boucher",
    "email": "bouanto@zoho.com",
    "time": "Mon Aug 03 12:29:11 2026 -0400"
  },
  "committer": {
    "name": "Antoni Boucher",
    "email": "bouanto@zoho.com",
    "time": "Mon Aug 03 12:29:11 2026 -0400"
  },
  "message": "doc: add the multi-target porting checklist\n\nPorts opt into multi-target builds by declaring multi_target_ready in\nconfig.gcc, and the declaration is a promise about the port\u0027s shape: prefixed\nexports, headers that compile in a captured context, macro values that no shared\nlayout depends on, descriptor coverage for anything host code reads. The manual\nnow walks a port maintainer through that checklist, each item tied to the\nmechanism that depends on it and to the identity gates that certify the result.\nThe blob contract closes the chapter: what a blob may export and what its fields\nmay reference, and how that narrowness lets the producer move from N generator\nruns with renames to merged target-indexed tables one generator at a time,\nwithout consumers or the registry ever changing.\n\ngcc/ChangeLog:\n\n\t* doc/multi-target.texi: Add the porting checklist and the producer\n\tcontract.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d42aa5e79eca09e24cfb0c51f47f1670750245a1",
      "old_mode": 33188,
      "old_path": "gcc/doc/multi-target.texi",
      "new_id": "47670fa330c60aeda186f14cd7665ac13fcafcec",
      "new_mode": 33188,
      "new_path": "gcc/doc/multi-target.texi"
    }
  ]
}