)]}'
{
  "commit": "d9fcbb06f2e39b5290f22ebc0e2c5076ae026ccd",
  "tree": "4e403692f3f16f670c6b211b5bd18a61c2d4a135",
  "parents": [
    "460e812369db398da34e14c9d40c3ecec06afaf1"
  ],
  "author": {
    "name": "Axel Huebl",
    "email": "axel.huebl@plasma.ninja",
    "time": "Thu Jun 24 14:44:21 2021 -0700"
  },
  "committer": {
    "name": "Brad King",
    "email": "brad.king@kitware.com",
    "time": "Tue Jul 13 09:47:51 2021 -0400"
  },
  "message": "FindMPI: Interrogate Cray compiler\n\nCray traditionally does not ship mpicc/mpic++ compiler wrappers.\nDue to that, the traditional CMake logic to find MPI is to *only*\nsupport MPI on Cray systems if either\n\n1. Cray Wrappers are used for compiling, or\n2. an auxiliary MPI executable is found.\n\nOn many new Exascale prototypes, using the Cray wrappers for develop\nwork is extremely painful. Vendors such as AMD and integrators such\nas HPE seem not to go well in lock-step in Cray programming envs,\nmaking offloading with Cray wrappers too challenging. On the other\nhand, using the working experimental Vendor compilers works well,\nas long as one does not need MPI.\n\nExtend the fallback MPI search logic by also interrogating the\nCC/cc/ftn binaries if found for their MPI flags. This does not\nchange existing logic, i.e. using the Cray wrappers directly, but\nprovides an additional way to get MPI programs compiled on Cray.\n\nFixes: #22368\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0b0d2d37480d1b75e1b8bd188064fed0e3322836",
      "old_mode": 33188,
      "old_path": "Modules/FindMPI.cmake",
      "new_id": "f64c4b8a1b8eeda390f2affee10bed640ad30553",
      "new_mode": 33188,
      "new_path": "Modules/FindMPI.cmake"
    }
  ]
}