python3kgae wrote: > I'm a little concerned about the strategy here. LLVM generally doesn't > explicitly capture padding it relies on the data layout rules to capture that. > > If this is the approach we're going with you can't put any vectors or > matrices into the cbuffer structure type and we need to account for all the > padding bytes explicitly.
Could you explain more about can't put any vectors or matrices into the cbuffer structure type? The issue is packoffset might generate gap in the layout. The datalayout cannot express the gap. If we cannot implement it with padding, the other option will be metadata. https://github.com/llvm/llvm-project/pull/91999 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
