)]}'
{
  "commit": "2e3aff27623b20b08ac58f8eaf73e97e58b4e67c",
  "tree": "4978e06f06bf6557021d629f04b4454a0c575b0d",
  "parents": [
    "a1ef65231b379e5b01fc2079d3fdc185c90d704c"
  ],
  "author": {
    "name": "Richard Bunt",
    "email": "richard.bunt@linaro.org",
    "time": "Mon Jun 12 09:27:14 2023 +0100"
  },
  "committer": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Mon Jun 12 12:32:52 2023 -0600"
  },
  "message": "gdb/testsuite: Testing with the armflang compiler\n\nCurrently the Fortran test suite does not run with armflang because the\ncompiler detection fails. This in turn means fortran_runto_main does not\nknow which main method to use to start a test case.\n\nFortran compiler detection was added in 44d469c5f85; however, the commit\nmessage notes that it was not tested with armflang.\n\nThis commit tests and fixes up a minor issue to get the detection\nworking.\n\nThe goal here is to get the tests running and preventing further\nregressions during future work. This change does not do anything to fix\nexisting failures.\n\n\u003eFrom what I can understand, the auto detection leverages the\npreprocessor to extract the Fortran compiler identity from the defines.\nThis preprocessor output is then evaluated by the test suite to import\nthese defines.\n\nIn the case of armflang, this evaluation step is disrupted by the\npresence of the following warning:\n\n    $ armflang -E -fdiagnostics-color\u003dnever testsuite/lib/compiler.F90 -o compiler.exp\n    $ clang-13: warning: argument unused during compilation: \u0027-fdiagnostics-color\u003dnever\u0027 [-Wunused-command-line-argument]\n\nThe evaluation logic is already set up to filter this warning, but the\nprefix differs.\n\nThis commit fixes the issue by updating the filter to exclude the\narmflang flavour of warning.\n\ngdb.fortran regression tests run with GNU, Intel and Intel LLVM. No\nregressions detected.\n\nThe gdb.fortran test results with ACfL 23.04.1 are as follows.\n\nBefore:\n\n # of expected passes\t\t560\n # of unexpected failures\t113\n # of unresolved testcases\t2\n # of untested testcases\t5\n # of duplicate test names\t2\n\nAfter:\n\n # of expected passes\t\t5388\n # of unexpected failures\t628\n # of known failures\t\t10\n # of untested testcases\t8\n # of unsupported tests\t\t5\n # of duplicate test names\t5\n\nAs can be seen from the above, there are now considerably more passing\nassertions.\n\nReviewed-By: Luis Machado \u003cluis.machado@arm.com\u003e\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3cdd73b7da3d44930c3401132118ac46105a00ba",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/gdb.exp",
      "new_id": "c3e5d4891dcbed2c1b3262ed2e19962750bbd8ee",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/gdb.exp"
    }
  ]
}