Interrupt instructions should write the stack

[hainest]

I didn't go diving into the code, so I'm not sure if the change would best be made in the json (to match the call instructions) or in the generator. I can make a PR, if folks could point me in the right direction on this (although my C# is very rusty).

  {
    "mnemonic": "int",
    "opcode": "CD",
    "operands": [
      {
        "operand_type": "imm",
        "encoding": "uimm8",
        "element_type": "uint8",
        "width16": 1,
        "width32": 1,
        "width64": 1
      },
      {
        "action": "write",
        "operand_type": "implicit_reg",
        "register": "ssz_ip",
        "visible": false
      }
    ],
    "meta_info": {
      "category": "INTERRUPT",
      "extension": "BASE",
      "isa_set": "I86"
    },
    "affected_flags": {
      "access": "must_write",
      "tf": "0",
      "if": "m",
      "iopl": "t",
      "nt": "m",
      "rf": "0",
      "vm": "t_m",
      "ac": "m",
      "vif": "m"
    },
    "comment": "SUNMQVNTOklOVA0KQVRUUklCVVRFUzpOT1RTWA0KQ1BMOjMNCkNBVEVHT1JZOklOVEVSUlVQVA0KRVhURU5TSU9OOkJBU0UNCklTQV9TRVQ6STg2DQpGTEFHUzpNVVNUIFsgdmlmLW1vZCBhYy1tb2Qgdm0tdHN0IHZtLW1vZCByZi0wIG50LW1vZCBpb3BsLXRzdCBpZi1tb2QgdGYtMCBdDQpQQVRURVJOOjB4Q0QgVUlNTTgoKQ0KT1BFUkFORFM6SU1NMDpyOmIgUkVHMD1ySVAoKTp3OlNVUFA="
  },

---

Intel SDM June 2025

[mappzor]

Thanks for reporting this, currently we are intensively iterating on the new generator and we avoid making changes to definitions themselves to avoid complicating validation. After merging changes in the main repo we plan to revisit all pending issues regarding operands actions and most likely handle them all in one go.

System instructions are always problematic because we don't model them fully. However I agree that stack write is a reasonable minimum.

By the way if you find more issues please report them in the main Zydis repo.