search for: mulsdrm_strict

...s right, then I’d need to introduce a new machine opcode for any instruction that I wanted to have an implicit register use. For instance, if we just mutated ISD::STRICT_FADD to ISD::FADD and Select changed that to X86::MULSDrm, then to attach implicit MXCSR use to that I’d need a new opcode (X86::MULSDrm_Strict) that behaves just like X86::MULSDrm but has the implicit MXCSR use/def information associated with it. Does it sound like I’m understanding this correctly? You're correct that implicit operands normally come from the instruction definitions, but you can add whatever other implicit operands y...