You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "constant" offsets are then only available via op.getConstantOffsets() and the regular via op.getOffsets(). The xegpu-to-vc-func pass only accesses regular offsets and ignores constant ones. Changing this line of code to op.getConstantOffsets() makes the "constant" offsets to work and the regular ones to be ignored. Is this intended behavior that one of the offsets type is ignored or is this a bug?
A constant offset is when you simply put a number as an offset value instead of an index value:
The "constant" offsets are then only available via
op.getConstantOffsets()
and the regular viaop.getOffsets()
. Thexegpu-to-vc-func
pass only accesses regular offsets and ignores constant ones. Changing this line of code toop.getConstantOffsets()
makes the "constant" offsets to work and the regular ones to be ignored. Is this intended behavior that one of the offsets type is ignored or is this a bug?reproducer
p.s. an example of how to use
xegpu.update_nd_offset
in mlir documentation uses "constant" offsets and as far as I understand IMEX llvm patches do not modify the structure ofupdate_nd_offset
, so I would expect them to work.The text was updated successfully, but these errors were encountered: