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
{{ message }}
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.
Not sure whether this is a bug or feature. I was trying figure out why certain apps have unaligned loads/stores when tile size is a multiple of burst size. And it turns out to be the type conversion on loop indices mess up constant propagation in spatial.
is a aligned load. because requestLength.s in DRAMTransfersInternal is not statically known. I would assume loop bound is already of type Index so .to[Index] effectively should be a no op?
The text was updated successfully, but these errors were encountered:
Not sure whether this is a bug or feature. I was trying figure out why certain apps have unaligned loads/stores when tile size is a multiple of burst size. And it turns out to be the type conversion on loop indices mess up constant propagation in spatial.
For example in GEMM_Blocked,
is a unaligned load while
is a aligned load. because
requestLength.s
inDRAMTransfersInternal
is not statically known. I would assume loop bound is already of type Index so.to[Index]
effectively should be a no op?The text was updated successfully, but these errors were encountered: