)]}'
{
  "commit": "e3457d211e2720dd0f8070fe7600be4b026ed1ef",
  "tree": "928b8f81b260dedb831650a08a22ec0a70c77faf",
  "parents": [
    "57da156bfc01865c716112e5582c39cd551e8b7a"
  ],
  "author": {
    "name": "Jeff Law",
    "email": "jeffrey.law@oss.qualcomm.com",
    "time": "Sun Sep 13 08:49:47 2026 -0600"
  },
  "committer": {
    "name": "Jeff Law",
    "email": "jeffrey.law@oss.qualcomm.com",
    "time": "Sun Sep 13 08:49:47 2026 -0600"
  },
  "message": "[RISC-V][PR target/127318] Attach DEF_CFA to correct insn\n\nAs is noted in the PR, the REG_CFA_DEF_DFA note is wrong for the testcase,\nwhile I get meaningfully different CFA note locations than the author, it is\nclear that the note is getting attached to the wrong insn.\n\nThe CFA_DEF_CFA note should get attached to the insn that copies from the stack\npointer into the temporary.  The RISC-V port tried to do that, but appears to\nhave just gotten the logic wrong.  The net is the CFA_DEF_CFA note got attached\nto the insn before the stack pointer copy.  Worse yet the insn with the note\ncould move around relative to the stack pointer for scheduling purposes.\n\nThe fix is trivial.  We just need to attach the note to the sp-\u003etemp copy.\nGiven this doesn\u0027t affect code generation, but is a correctness issue, I will\ngo ahead and backport it immediately rather than waiting for the usual simmer\non the trunk.\n\nBootstrapped and regression tested on the K3 and c920.  Also tested for the\nriscv32-elf and riscv64-elf platforms.\n\n\tPR target/127318\ngcc/\n\t* config/riscv/riscv.cc (riscv_v_adjust_scalable_frame): Attach\n\tREG_CFA_DEF_CFA note to the copy from the stack pointer.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "58c48bd1627ce08e9e97acb372f696f78815b2b6",
      "old_mode": 33188,
      "old_path": "gcc/config/riscv/riscv.cc",
      "new_id": "39309b2b2058a17062db0586c8954ae40f9d357f",
      "new_mode": 33188,
      "new_path": "gcc/config/riscv/riscv.cc"
    }
  ]
}