SharmaRithik wrote:

 Thanks for adding the `_BitInt(19)` tests. Does the same issue still remain 
for `!cir.vector<3 x !s32i>`? Its current `getTypeSize()` is 12 bytes but 
advancing a pointer by one element uses 16 bytes. Would `cir.ptr_stride` 
calculate 12 here? Should `VectorType` report the padded size or should this 
code use the allocation size?

https://github.com/llvm/llvm-project/pull/219047
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to