)]}'
{
  "commit": "2f79f2e767c167f289d00c02dc43832c0fc2faec",
  "tree": "ecd3f0da859392fd0d542785e77683e6a69ff0b8",
  "parents": [
    "6891aaf70bb09317138121f534cb84cb5134e89a"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Sat Mar 18 15:15:49 2023 +0000"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Thu Mar 23 07:19:02 2023 +0000"
  },
  "message": "gdb/riscv: add systemtap support\n\nThis commit is initial support for SystemTap for RISC-V Linux.  The\nfollowing two tests exercise SystemTap functionality, and are showing\nmany failures, which are all fixed by this commit:\n\n  gdb.cp/exceptprint.exp\n  gdb.base/stap-probe.exp\n\nOne thing I wasn\u0027t sure about is if the SystemTap support should be\nLinux specific, or architecture specific.  For aarch64, arm, ia64, and\nppc, the SystemTap support seems to libe in the ARCH-linux-tdep.c\nfile, while for amd64, i386, and s390 the implementation lives in\nARCH-tdep.c.  I have no idea which of these is the better choice -- or\nmaybe both choices are correct in the right circumstances, and I\u0027m\njust not aware of how to choose between them.\n\nAnyway, for this patch I selected riscv-tdep.c (though clearly, moving\nthe changes to riscv-linux-tdep.c is trivial if anyone thinks that\u0027s a\nmore appropriate location).\n\nThe stap-probe.exp file tests immediate, register, and register\nindirect operands, all of which appear to be working fine with this\ncommit.  The generic expression support doesn\u0027t appear to be\narchitecture specific, so I\u0027d expect that to work fine too.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "388ce8c2519bf5dd8911aa91949e25c69f56c6df",
      "old_mode": 33188,
      "old_path": "gdb/riscv-tdep.c",
      "new_id": "8024ffed3c2112ca8ece86a16d9b1725a3d83edc",
      "new_mode": 33188,
      "new_path": "gdb/riscv-tdep.c"
    }
  ]
}