search for: isv1

...a later version this was changed to 'LD.32'. The semantics and schedule remained the same, but in the TD file I had to introduce two 'def's for this (actually, I abstract a bit more and use a 'defm'): def LD32_v1 : Instr<... "LD32" ...>, Requires<[isV1]>; def LD32_v2 : Instr<... "LD.32" ...>, Requires<[isV2]>; This all works fine, but there is a large number of them which makes maintenance difficult. This also adds to the burden of selection when using 'BuildMI' in the C++ code, as I have to do things like:...

...one version of the chip, but for a later version this was changed to ‘LD.32’. The semantics and schedule remained the same, but in the TD file I had to introduce two ‘def’s for this (actually, I abstract a bit more and use a ‘defm’): def LD32_v1 : Instr<... “LD32” ...>, Requires<[isV1]>; def LD32_v2 : Instr<... “LD.32” ...>, Requires<[isV2]>; This all works fine, but there is a large number of them which makes maintenance difficult. This also adds to the burden of selection when using ‘BuildMI’ in the C++ code, as I have to do things like: if (isV1())...