)]}'
{
  "commit": "a815cdb41312bc3b8536dcb5a2cf2c263c3418f8",
  "tree": "afa3d08cc1ca5bc85209bba7b5b1d899c61c2c9d",
  "parents": [
    "e4a41dc43a32ed4d43ca4ffbe099c14feb73c01d"
  ],
  "author": {
    "name": "Hans-Peter Nilsson",
    "email": "hp@axis.com",
    "time": "Sat Jan 24 04:53:41 2026 +0100"
  },
  "committer": {
    "name": "Hans-Peter Nilsson",
    "email": "hp@bitrange.com",
    "time": "Sat Jan 24 06:12:56 2026 +0100"
  },
  "message": "ld: Make separate clauses where a label was before a declaration\n\nThe default behavior of gcc changed from gcc-11.  With gcc-10 and\nearlier versions, you got:\n\nIn file included from ../bfd/bfd.h:45,\n                 from /src/ld/ldmisc.c:23:\n/src/ld/ldmisc.c: In function \u0027vfinfo\u0027:\n/src/ld/ldmisc.c:186:8: error: a label can only be part of a statement and a declaration is not a statement\n  186 |        bool ll_type \u003d false;\n      |        ^~~~\n/src/ld/ldmisc.c:581:8: error: a label can only be part of a statement and a declaration is not a statement\n  581 |        bool ll_type \u003d false;\n      |        ^~~~\nmake[4]: *** [Makefile:1606: ldmisc.o] Error 1\n\nSince gcc-10 matches the binutils/README requirement (\"a C99 compliant\ncompiler and library\") and as binutils policy is to adjust code to\nhandle earlier gcc versions, an obvious fix is to make a compound\nstatement for the code after the case-label.\n\nld:\n\n\t* ldmisc.c (vfinfo) \u003ccase \u0027l\u0027 - two cases\u003e: Make separate\n\tcompound statements where case-labels were part of a declaration.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3deceb76719240320c49c3cbd63bfa339d763e08",
      "old_mode": 33188,
      "old_path": "ld/ldmisc.c",
      "new_id": "f39e0a3dbe7c3cbce08a8985b3724bd9b66b3b94",
      "new_mode": 33188,
      "new_path": "ld/ldmisc.c"
    }
  ]
}