)]}'
{
  "commit": "c61b7b7b8ea5e3a55b4642dade4798e5c896df66",
  "tree": "db5e3ac4209b78dbad7374778d087e55371102fd",
  "parents": [
    "d7f0f10189fa83a73d9819e81fd321142c0c6398"
  ],
  "author": {
    "name": "Alan Modra",
    "email": "amodra@gmail.com",
    "time": "Tue Mar 28 20:25:26 2023 +1030"
  },
  "committer": {
    "name": "Alan Modra",
    "email": "amodra@gmail.com",
    "time": "Tue Mar 28 21:04:30 2023 +1030"
  },
  "message": "Avoid undefined behaviour in m68hc11 md_begin\n\nGiven p \u003d A where p is a pointer to some type and A is an array of\nthat type, then the expression p - 1 + 1 evokes undefined behaviour\naccording to the C standard.\n\ngcc-13 -fsanitize\u003daddress,undefined complains about this, but not\nwhere the undefined behaviour actually occurs at tc-m68hc11.c:646.\nInstead you get an error: \"tc-m68hc11.c:708:20: runtime error: store\nto address 0x62600000016c with insufficient space for an object of\ntype \u0027int\u0027\".  Which is a lie.  There most definitely is space there.\nOh well, diagnostics are sometimes hard to get right.  The UB is easy\nto avoid.\n\n\tPR 30279\n\t* config/tc-m68hc11.c (md_begin): Avoid undefined pointer\n\tdecrement.  Remove unnecessary cast.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7438e0dd51dadb5284d05c6aa828da6372243070",
      "old_mode": 33188,
      "old_path": "gas/config/tc-m68hc11.c",
      "new_id": "270ddf999ce10c482f6b8aa67167d01c285a0308",
      "new_mode": 33188,
      "new_path": "gas/config/tc-m68hc11.c"
    }
  ]
}