)]}'
{
  "commit": "ed2aa304cac86e7fa88cd271c2d73ffd9e324e22",
  "tree": "b11fae1d887f662a63389b4cae08e0f37751c967",
  "parents": [
    "dcf853df8fda885cafbc02f916ef01684b7d1104"
  ],
  "author": {
    "name": "Craig Topper",
    "email": "craig.topper@sifive.com",
    "time": "Tue Feb 03 22:42:05 2026 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Feb 03 22:42:05 2026 -0800"
  },
  "message": "[RISCV] Use RVInstVV as the base for CustomSiFiveVMACC. NFC (#179565)\n\nThis correctly names the operands vd, vs1, and vs2 instead of rd, rs1,\nand rs2. RVInstVCCustom2 is now only used for VCIX which has its own\noperand naming problems.\n\nI\u0027m considering using named operand indices in\nRISCVAsmParser::validateInstruction for the RVVConstraints, but first I\nwould have to make vs1, vs2 named correctly across all vector\ninstructions.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4516ba9f79a1b286dd1f90fae85d2940ff23c826",
      "old_mode": 33188,
      "old_path": "llvm/lib/Target/RISCV/RISCVInstrInfoXSf.td",
      "new_id": "5723f3ac0c02ffe0afcf98d90ede2d59a383db93",
      "new_mode": 33188,
      "new_path": "llvm/lib/Target/RISCV/RISCVInstrInfoXSf.td"
    }
  ]
}