I have been reading an old article:
http://msdn.microsoft.com/en-us/library/Aa290049
It talks about memory alignment issue using C/C++ as example.
Is the issue in that article still relevant to F90 module definition? I would think the same principle still applies.
We have a house of f90 developers who just keep appending load of members to existing module definitions, and data alignment has never been in their consideration. We do use compilation option such as "/real_size:64 /align:rec16byte /align:qcommons /align:sequence" (we do not set anything for array alignment though)
Would there be any potential performance enhancement if we start to align module members to 16bytes boundary, instead of relying on compiler to handle it?
Any good reference?