-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unaligned data warnings with Intel compiler #34
Comments
-fixed issue #34 by rearranging the variable in json_value -some internal refactoring. -all changes backward compatible for ifort and gfortran.
Should be fixed now. |
Hi all, I am not sure why you used "sequence" attribute (I read your developments, This is just a reminder, in many case this is not relevant, but I was not See you soon. Il giorno 03:07 gio 08/gen/2015 Jacob Williams notifications@github.com
|
The SEQUENCE was because I'm using it an argument in a DLL subroutine. See: https://software.intel.com/en-us/forums/topic/538073 . I'll do some speed tests to see if it is causing a significant performance penalty. |
I think that if the memory alignment warnings issued by ifort have been addressed this shouldn't be a big issue. |
I am not sure, but I think it is more complicated. For example there are situations where the components of a derived type should be not aligned for memory optimization, thus the compiler use memory padding to optimize the derived type memory handling (for caching/prefetching and similar obscure nerd-details :-) ). Sequence prevent memory padding... I think that in this case the use of sequence has not relevant consequences on performances, but if there is the time to check it, this is a plus. This is just a remainder due to my paranoiac nature. See you soon. |
Commit 0066f7d (where a SEQUENCE attribute was added to
json_value
type) is causing unaligned data warnings to be issued by the Intel fortran compiler (v2015). A fix is in the works.The text was updated successfully, but these errors were encountered: