This was only applying the deeper nested zext pattern, and missing the
special case code size fold.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Will it correctly work with and without sram-ecc? I.e. do we have any assumptions about high 16 content of an i16 value anywhere?
Comment Actions
That only matters for memory accesses as far as I know. This isn't really a new pattern, and the existing predicates don't check
Comment Actions
It is more than memory as far as I know, even arithmetic instructions will either zero or preserve the high bits.
Comment Actions
This is controlled by a bit starting in gfx9 I think. Eventually we need to split the instruction definitions to add a tied operand for the preserved high case. These are separate problems from this patch anyway