)]}'
{
  "commit": "c32277bbf2e53f9eb61db7e8ce15f83adf30e490",
  "tree": "e72295db749de0d6fe541386ed168278c20d4338",
  "parents": [
    "d71ef546a89548d5c04f47c272741583193abc8d"
  ],
  "author": {
    "name": "Andrei Elovikov",
    "email": "andrei.elovikov@sifive.com",
    "time": "Fri Feb 20 11:33:45 2026 -0800"
  },
  "committer": {
    "name": "Andrei Elovikov",
    "email": "andrei.elovikov@sifive.com",
    "time": "Tue Jun 30 09:18:26 2026 -0700"
  },
  "message": "[NFC][VPlan] Add initial tests for future VPlan-based stride MV\n\nI tried to include both the features that current\nLoopAccessAnalysis-based transformation supports (e.g., trunc/sext of\nstride) but also cases where the current implementation behaves poorly,\ne.g., https://godbolt.org/z/h31c3zKxK; as well as some other potentially\ninteresting scenarios I could imagine.\n\nThe are two test files with the same content. One is for VPlan dump change of\nthe future transformation alone (I\u0027ll update `-vplan-print-after` in the next\nPR), another is for the full vectorizer pipeline. The latter have two `RUN:`\nlines:\n * No multiversioning, so the next PR diff can show the transformation itself\n * Stride multiversionin performed in LAA, so that we can compare future\n   VPlan-based transformation vs old behavior.\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "09f4b71594185e51c897420de534a3213fc77812",
      "new_mode": 33188,
      "new_path": "llvm/test/Transforms/LoopVectorize/VPlan/vplan-based-stride-mv.ll"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "94159c61ee07f6b9ebbc93d9cbc3214e7037d1d9",
      "new_mode": 33188,
      "new_path": "llvm/test/Transforms/LoopVectorize/vplan-based-stride-mv.ll"
    }
  ]
}