)]}'
{
  "commit": "ff656e2e1cb1592617a0bb4b21538d3cea17c24f",
  "tree": "424a98771925f86407c10504ad52f40aa5dbf7f9",
  "parents": [
    "e66b7536b7ffbbe1eb77c6679d558114cd3f5893"
  ],
  "author": {
    "name": "Tiezhu Yang",
    "email": "yangtiezhu@loongson.cn",
    "time": "Wed Jan 12 08:31:02 2022 +0800"
  },
  "committer": {
    "name": "Tiezhu Yang",
    "email": "yangtiezhu@loongson.cn",
    "time": "Wed Jan 12 08:31:02 2022 +0800"
  },
  "message": "gdb: testsuite: fix failed testcases in gdb.base/charset.exp\n\nIn gdb/testsuite/gdb.base/charset.c, the last argument is greater than 127\nwhen call fill_run() in EBCDIC-US and IBM1047, but the type of string[] is\nchar, this will change the value due to sign extension.\n\nFor example, ebcdic_us_string[7] will be -63 instead of the original 193 in\nEBCDIC-US.\n\nMake the type of string[] as unsigned char to fix the following six failed\ntestcases:\n\n  $ grep FAIL gdb/testsuite/gdb.sum\n  FAIL: gdb.base/charset.exp: check value of parsed character literal in EBCDIC-US\n  FAIL: gdb.base/charset.exp: check value of parsed string literal in EBCDIC-US\n  FAIL: gdb.base/charset.exp: check value of escape that doesn\u0027t exist in EBCDIC-US\n  FAIL: gdb.base/charset.exp: check value of parsed character literal in IBM1047\n  FAIL: gdb.base/charset.exp: check value of parsed string literal in IBM1047\n  FAIL: gdb.base/charset.exp: check value of escape that doesn\u0027t exist in IBM1047\n\nSigned-off-by: Tiezhu Yang \u003cyangtiezhu@loongson.cn\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ed9387b926d8ebe29bf1ed27a37f5c9ebafb578e",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/charset.c",
      "new_id": "98aa100f291d58146ac27446fed534a8ba880f88",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/charset.c"
    }
  ]
}