)]}'
{
  "commit": "03a68377235b2305ef328e4eb20efdd2c95b8bcd",
  "tree": "0e79012f21c688f7b9128181e6fde74f433a223e",
  "parents": [
    "fe8ab97ca6973c136d9cf0abb3e8df488e195e91"
  ],
  "author": {
    "name": "Rupert Swarbrick",
    "email": "rswarbrick@lowrisc.org",
    "time": "Thu Oct 15 14:08:31 2020 +0100"
  },
  "committer": {
    "name": "Rupert Swarbrick",
    "email": "rswarbrick@gmail.com",
    "time": "Tue Oct 27 09:51:22 2020 +0000"
  },
  "message": "[memutil] Load ELF files via a staging area\n\nThis doesn\u0027t change the behaviour of LoadElfToMemories (the core of\nmemutil\u0027s ELF loading code), but the function now works in two stages.\nThe first stage loads the code into segments that are split between\nthe named memories (stored in staging_area_). The second stage\niterates over these memories and segments loading them into the\nmemory.\n\nOf course, the point of this is that we can choose to do just the\nfirst stage (by calling StageElf) and then programmatically get at the\nsegments. This will be used by a following commit to expose the\ncontents of the ELF over DPI to the OTBN testbench.\n\nSigned-off-by: Rupert Swarbrick \u003crswarbrick@lowrisc.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c9f3572970ed792c3d1f4de5a4840a1008bbfcbc",
      "old_mode": 33188,
      "old_path": "hw/dv/verilator/cpp/dpi_memutil.cc",
      "new_id": "59c38c07ab2da40ac5d30674c94129c0e3f17468",
      "new_mode": 33188,
      "new_path": "hw/dv/verilator/cpp/dpi_memutil.cc"
    },
    {
      "type": "modify",
      "old_id": "de86b2fb242c6b6c6fab1472a57668204ad77472",
      "old_mode": 33188,
      "old_path": "hw/dv/verilator/cpp/dpi_memutil.h",
      "new_id": "f37ef97ccb3910c8d82a3da819a8227a6f69be03",
      "new_mode": 33188,
      "new_path": "hw/dv/verilator/cpp/dpi_memutil.h"
    }
  ]
}