If there's any padding between record's fields because of differently sized datatypes, you could also try reordering the fields. For example, if you mix booleans with integers (which misaligns them if the record is packed), put the integer fields before all the booleans, etc.
my projects https://github.com/dpethes
You're essentially dealing with two devices, the CPU and the GPU - both access structured/ordered data in their own way - so when transferring data between the two? a factor such as record byte alignment can't be assumed in any case where the GPU and CPU could potentially differ. So in all cases on any platform - I would recommend that knowing and managing data alignment be considered part of standard best practice as is knowing and managing platform endiness.
When the moon hits your eye like a big pizza pie - that's an extinction level impact event.
Posting Permissions
Reply With Quote
Bookmarks