)]}'
{
  "commit": "ce3f9039d925781a462d3c7e5be32fe2e5079a21",
  "tree": "972a210be2bb0739091cf8f5c333ad3051d6c632",
  "parents": [
    "5a875b8580f8fedebda7f5deca95059581703ee7",
    "783780c25312d0eb78511e33fa572a5c3feb8dfd"
  ],
  "author": {
    "name": "Matthias Krüger",
    "email": "476013+matthiaskrgr@users.noreply.github.com",
    "time": "Sat Dec 20 13:46:00 2025 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sat Dec 20 13:46:00 2025 +0100"
  },
  "message": "Rollup merge of #148991 - RalfJung:genmc-exit, r\u003doli-obk\n\nmiri genmc: fix exit() handling\n\nIn genmc mode, Miri does not want to stop execution when `exit` is called. Instead we want to continue running other threads to ensure we covered all possible concurrent behaviors (including the ones where the exiting thread was delayed so the other threads took their turns first). However, the core interpreter has a sanity check that prevents us from just doing nothing in `exit`. This leaves us in a pickle: there\u0027s nowhere we can jump to (exit has return type `!` so there\u0027s no next block), but if we don\u0027t jump anywhere we ICE.\n\nThe first commit fixes that by disabling the sanity check when there is no block to jump to. That still catches the mistake of forgetting to jump for the vast majority of shims.\n\nWe currently don\u0027t build Miri\u0027s genmc integration in rustc CI so I had to hack the feature into the bootstrap miri integration. That turned out to use the wrong Miri binary, which is fixed by the second commit: we can just rely on CARGO_BIN_EXE_miri, there\u0027s no need for a MIRI environment variable.\n\nr? ``@oli-obk``\n",
  "tree_diff": []
}