Check object alignment at runtime.

[giuliomoro]

This will throw at runtime when the allocator didn't respect the object's alignment. This can only happen with heap allocation when using a standard earlier than c++17 . See discussion in #54

[falkTX]

if using the code in a plugin context, throwing is quite bad. also impossible to catch and recover if using C (for which hvcc has bindings for afaik)
IMO it would be best to make this deactivate the module with an error of sorts (printing to console?)

[giuliomoro]

Fair point, but this check is to detect an alignment issue at allocation time. Operating on misaligned memory would cause a SIGILL to be delivered to your process when later on you try to execute SIMD assembly on unaligned memory. So it's much better - imo - to detect the issue at allocation time. It's C++ convention that a failed object construction should throw, so it should be up to the calling code to look out for this as appropriate. The provided C wrapper is already safe as it is* because it ensures alignment before calling new();

• at least it guarantees alignment to a 16 byte boundary