)]}'
{
  "commit": "577bcb8364eb792edad5d096868476f7054a8249",
  "tree": "20efb1d57695324cf45ed3689104b0250644597c",
  "parents": [
    "bd3d9eaa87afe81f6a79a9c47c4d25e1181da625"
  ],
  "author": {
    "name": "Rupert Swarbrick",
    "email": "rswarbrick@lowrisc.org",
    "time": "Wed Jan 20 12:48:42 2021 +0000"
  },
  "committer": {
    "name": "Rupert Swarbrick",
    "email": "rswarbrick@gmail.com",
    "time": "Wed Jan 20 14:37:09 2021 +0000"
  },
  "message": "[otbn] Change how we describe valid ranges for PC-relative operands\n\nIt used to look something like this:\n\n  Valid range: .-1048576 to .+1048574 in steps of 2\n\nAnd is now expanded quite a lot to be super-explicit:\n\n  Valid range: -1048576 to 1048574 in steps of 2. This is encoded\n  PC-relative but appears as an absolute value in assembly. To write a\n  raw value in an assembly file, write something in the range\n  .-1048576 to .+1048574.\n\nSigned-off-by: Rupert Swarbrick \u003crswarbrick@lowrisc.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "033bf963243ea2ed75221efd3ff53248d30c8de5",
      "old_mode": 33188,
      "old_path": "hw/ip/otbn/util/shared/operand.py",
      "new_id": "97109a1abce7aa9f749d52354858ba4c442362f4",
      "new_mode": 33188,
      "new_path": "hw/ip/otbn/util/shared/operand.py"
    }
  ]
}