search for: ginst

...the rest of TableGen. Consider combine rules defined in multiclasses, for example. That is very common all through LLVM. In order to mirror an existing selection rule in the AMDGPU backend, we'd likely want to have something like this: > > multiclass Arithmetic_i16_GIPats<Instruction ginst, > Instruction inst> { > // This is probably wishful thinking -- would be okay if we had to > // split this into two different rules due to the different types > // of $dst > def : GICombineRule< > (defs root:$dst, operand:$...

...eGen. Consider combine rules defined in multiclasses, for example. That is very common all through LLVM. In order to mirror an existing selection rule in the AMDGPU backend, we'd likely want to have something like this: >>> >>> multiclass Arithmetic_i16_GIPats<Instruction ginst, >>> Instruction inst> { >>> // This is probably wishful thinking -- would be okay if we had to >>> // split this into two different rules due to the different types >>> // of $dst >>> def : GICombineRule&...

Hi All, I've been working on the GlobalISel combiner recently and I'd like to share the plan for how Combine Rules will be defined in GlobalISel and solicit feedback on it. This email ended up rather long so: TL;DR: We're planning to define GlobalISel Combine Rules using MIR syntax with a few bits glued on to interface with the algorithm and escape into C++ when we need to.