)]}'
{
  "commit": "388f63c18f523ca32199adef33dbacbeeed3b62a",
  "tree": "da58df97ef4ff0f371b64cc39bae3c9a57c03ab7",
  "parents": [
    "f0f6df0a04fe521ff4df9b74981a624fa2583e3a"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri May 12 11:43:41 2023 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri May 12 11:43:41 2023 +0200"
  },
  "message": "[gdb/testsuite] Make is_64_target more robust\n\nI ran test-case gdb.dwarf2/opt-out-not-implptr.exp with make-check-all.sh, and\nwith target board dwarf64 ran into:\n...\nFAIL: gdb.dwarf2/opt-out-not-implptr.exp: print noptr\n...\ndue to is_target_64 failing because of:\n...\nbuiltin_spawn -ignore SIGHUP gcc -fno-stack-protector \\\n  -fdiagnostics-color\u003dnever -w -c -gdwarf64 -g -o is_64_target.o \\\n  is_64_target.c^M\ngcc: error: \u0027-gdwarf64\u0027 is ambiguous; use \u0027-gdwarf-64\u0027 for DWARF version or \\\n  \u0027-gdwarf -g64\u0027 for debug level^M\ncompiler exited with status 1\n...\n\nThe FAIL is the same FAIL I run into with target board unix/-m32: is_target_64\nfails for both cases.\n\nThe reason that is_target_64 is failing for target board dwarf64, is because\nof using system compiler 7.5.0 which doesn\u0027t support -gdwarf64.\n\nFix this by making is_target_64 use nodebug instead of debug for compilation.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "50c10333df1a620dc20600de51874686301c8d8b",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/gdb.exp",
      "new_id": "010da097766fd704f80e8b6228ce03a27d1b3752",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/gdb.exp"
    }
  ]
}
