)]}'
{
  "commit": "08ede4fbbe6d38e08bcc72c4df2cf6720b9f4717",
  "tree": "1edf02acd8c9ac9dd52f2ca337502c3c55abb16f",
  "parents": [
    "c109d79f5bc4d4e2b65c6ee284a3d853c0173d7d"
  ],
  "author": {
    "name": "Iain Sandoe",
    "email": "iain@sandoe.co.uk",
    "time": "Tue Aug 04 09:44:46 2026 +0100"
  },
  "committer": {
    "name": "Iain Sandoe",
    "email": "iain@sandoe.co.uk",
    "time": "Wed Aug 05 20:05:02 2026 +0100"
  },
  "message": "c++/objective-c++; Do not claim feature(modules), it is clang-specific.\n\nIt appears that we misinterpreted the modules feature and that it is intended\nto signal that the compiler supports \"clang modules\".  These are a similar\napproach to PCH and tightly coupled to clang AST - so not something that we\nare realistically likely to implement.\n\nUnfortunately, the macOS SDKs use this feature test to decide on some\nheader declaration ordering where it needs to change for clang modules.\n\nThis causes a fail to build the std. module sources on macOS meaning that we\nget an empty std.cc. Our intention should be parity with/without -fmodules.\n\nThe solution is not to claim feature(modules) - C++20 modules are gated on\n__cpp_module and so do not need it.\n\ngcc/cp/ChangeLog:\n\n\t* cp-objcp-common.cc: Remove claim to support clang modules.\n\nSigned-off-by: Iain Sandoe \u003ciain@sandoe.co.uk\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0a67aa8ce14b3607d518ad8a076e1f9851da964e",
      "old_mode": 33188,
      "old_path": "gcc/cp/cp-objcp-common.cc",
      "new_id": "8c9930bb2f37b31875782a50a029acd7e754052b",
      "new_mode": 33188,
      "new_path": "gcc/cp/cp-objcp-common.cc"
    }
  ]
}