)]}'
{
  "commit": "2df82cd4b459fbc32120e0ad1ce19e26349506fe",
  "tree": "5d883d8bf0fabe5bb76245e8259cf633dd8ea0d4",
  "parents": [
    "6576bffe6cbbb53c5756b2fccd2593ba69b74cdf"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Tue Nov 01 10:36:59 2022 +0000"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Tue Nov 01 10:50:50 2022 +0000"
  },
  "message": "opcodes/arm: silence compiler warning about uninitialized variable use\n\nThe earlier commit:\n\n  commit 6576bffe6cbbb53c5756b2fccd2593ba69b74cdf\n  Date:   Thu Jul 7 13:43:45 2022 +0100\n\n      opcodes/arm: add disassembler styling for arm\n\nwas causing a compiler warning about a possible uninitialized variable\nusage within opcodes/arm-dis.c.\n\nThe problem is in print_mve_unpredictable, and relates to the reason\nvariable, which is set by a switch table.\n\nCurrently the switch table does cover every valid value, though there\nis no default case.  The variable switched on is passed in as an\nargument to the print_mve_unpredictable function.\n\nLooking at how print_mve_unpredictable is used, there is only one use,\nthe second argument is the one that is used for the switch table,\nlooking at how this argument is set, I don\u0027t believe it is possible\nfor this argument to take an invalid value.\n\nSo, I think the compiler warning is a false positive.  As such, my\nproposed solution is to initialize the reason variable to the string\n\"??\", this will silence the warning, and the \"??\" string should never\nend up being printed.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6d302ec50bab1b54fcd36c32f2957ff770f4bf07",
      "old_mode": 33188,
      "old_path": "opcodes/arm-dis.c",
      "new_id": "101b3f84dfe1a3d2103fe8c519dfebcb48537fb9",
      "new_mode": 33188,
      "new_path": "opcodes/arm-dis.c"
    }
  ]
}