)]}'
{
  "commit": "a0bfd1bfa6e7ecdf67bbf11defeb821d9c63e8ef",
  "tree": "8351e56453dcaabd59d2c6f100fd8d3167b0ad72",
  "parents": [
    "b4b9074dc0dfab4fb00562b359315d78b09a1564"
  ],
  "author": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Wed Sep 20 09:16:19 2023 -0600"
  },
  "committer": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Mon Oct 30 07:45:39 2023 -0600"
  },
  "message": "Fix \"finish\" for vector types on ARM\n\nOn a big-endian ARM system, \"finish\" printed the wrong value when\nfinishing from a function that returned a vector type.  Similarly,\ncalls to a function also resulted in the wrong value being passed.  I\nthink both the read- and write-functions here should ignore the\nendian-ness.\n\nI tested this using the AdaCore internal test suite; the test case\nthat caught this is identical to gdb.base/gnu_vector.exp.\n\nApproved-By: Luis Machado \u003cluis.machado@arm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ab0df0f16a8f385c7649427dd1e9559f412b8663",
      "old_mode": 33188,
      "old_path": "gdb/arm-tdep.c",
      "new_id": "493e5b84758b1bd99fcb13bd1069b8ed2bcf42ac",
      "new_mode": 33188,
      "new_path": "gdb/arm-tdep.c"
    }
  ]
}