Go to file
Robert Maynard 763949351f Stop trying to align vtkm types. Read the full comments on why.
Using alignment on basic types when vtkm only targetted Linux/BSD/OSX was
'okay' because of how the alignment operators worked, but potential was going
to cause issues in the long run if we failed to detect the correct size and the
compiler was than forced to not use intrinsics.

Now with adding windows support we have run into another problem. Basically
using an alignment operator on a typedef means that the type must never
be passed by value, but must always be passed by reference. The reason for
this is that passing by value doesn't respect alignment requirements, and
can cause very subtle errors or crashes.

A really good read for people more interested in these problems:

http://eigen.tuxfamily.org/dox/group__TopicPassingByValue.html
http://eigen.tuxfamily.org/dox-devel/group__DenseMatrixManipulation__Alignement.html
2014-05-19 14:27:37 -04:00
CMake Properly name the VTKm CMakeFiles. 2014-02-11 14:56:03 -05:00
docs revise the header guard naming convention to not conflict with macro names. 2014-03-07 10:22:36 -05:00
vtkm Stop trying to align vtkm types. Read the full comments on why. 2014-05-19 14:27:37 -04:00
CMakeLists.txt Add in the basic CMake Infrastructure required for vtkm. 2014-02-10 15:00:17 -05:00
LICENSE.txt Add a license to vtkm. 2014-02-10 15:00:17 -05:00
README.md Initial commit. 2014-02-04 15:08:03 -05:00

Welcome to vtkm design and hackathon.

Resources:

EAVL: https://github.com/jsmeredith/EAVL DAX: https://github.com/Kitware/DaxToolkit