diff options
author | Benoit Jacob <jacob.benoit.1@gmail.com> | 2009-09-18 22:01:49 -0400 |
---|---|---|
committer | Benoit Jacob <jacob.benoit.1@gmail.com> | 2009-09-18 22:01:49 -0400 |
commit | 0b426ea00d39d54e2a7e9e2aef93e7f17aa12a54 (patch) | |
tree | 3ecb77ecbae63bd8acbff42f1e85cda1d7036ce5 | |
parent | add5381be7cb1d32ee1e3603a0b999f74abaf612 (diff) |
update page to explain how to get rid of it
-rw-r--r-- | doc/D11_UnalignedArrayAssert.dox | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/D11_UnalignedArrayAssert.dox b/doc/D11_UnalignedArrayAssert.dox index e95c767b4..226b20452 100644 --- a/doc/D11_UnalignedArrayAssert.dox +++ b/doc/D11_UnalignedArrayAssert.dox @@ -21,6 +21,7 @@ There are 4 known causes for this issue. Please read on to understand them and l - \ref c3 - \ref c4 - \ref explanation + - \ref getrid \section where Where in my own code is the cause of the problem? @@ -101,6 +102,16 @@ Eigen normally takes care of these alignment issues for you, by setting an align However there are a few corner cases where these alignment settings get overridden: they are the possible causes for this assertion. +\section getrid I don't care about vectorization, how do I get rid of that stuff? + +Two possibilities: +<ul> + <li>Define EIGEN_DONT_ALIGN. That disables all 128-bit alignment code, and in particular everything vectorization-related. But do note that this in particular breaks ABI compatibility with vectorized code.</li> + <li>Or define both EIGEN_DONT_VECTORIZE and EIGEN_DISABLE_UNALIGNED_ARRAY_ASSERT. This keeps the 128-bit alignment code and thus preserves ABI compatibility.</li> +</ul> + +For more information, see <a href="http://eigen.tuxfamily.org/index.php?title=FAQ#I_disabled_vectorization.2C_but_I.27m_still_getting_annoyed_about_alignment_issues.21">this FAQ</a>. + */ } |