)]}'
{
  "commit": "6911239bbaa7b4365d3d0ff7b6cb296cfe43480c",
  "tree": "fa725903db20973fc68d429315318f2052d6c83f",
  "parents": [
    "c963bda81e255dbac7c1acd31121d282a4910308"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Fri Nov 11 15:21:56 2022 +0000"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Fri Nov 18 11:21:36 2022 +0000"
  },
  "message": "gdb/testsuite: don\u0027t avoid DWARF assembler tests with Clang\n\nTwo tests make the claim that the DWARF assembler requires gcc,\nhowever, this isn\u0027t true.  I think at one point, when the DWARF\nassembler was first added, we did use some techniques that were not\nportable (see the comments in lib/dwarf.exp on function_range for\ndetails), however, I think most DWARF assembler tests will now work\nfine with Clang.\n\nThe two tests that I modify in this commit both work fine with Clang,\nat least, I\u0027ve tested with Clang 9.0.1 and 15.0.2, and don\u0027t see any\nproblems, so I\u0027m removing the early return logic that stops these\ntests from running with Clang.\n\nReviewed-By: Lancelot SIX \u003clancelot.six@amd.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6396b6650c1ce0a413f38b2f922051ef173a3ab7",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/until-trailing-insns.exp",
      "new_id": "56f6cf038e2f29214a2cf5a98299bb01d4a55e8c",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/until-trailing-insns.exp"
    },
    {
      "type": "modify",
      "old_id": "96ed25dd5d14bb75659bced87be6bef4795dae32",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.cp/incomplete-type-overload.exp",
      "new_id": "024014d68ba6cbfad0db55cbce13abc96c9d62bd",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.cp/incomplete-type-overload.exp"
    }
  ]
}