Test fixes

[chbaker0]

I fixed a compiler error and various undefined behavior I found in the unit tests.

[Groovounet]

I don't think chbaker0@ff1581d is acceptable. Fixing warnings by converting to double? I fixed the warnings using %ld instead.

[chbaker0]

std::clock_t is totally unspecified though; it can be an int, a long int, a float, a double, etc. The only safe and portable thing to do is cast it to double and print it as such. Or, better yet, use a better clock timing API. chrono is much better, for example.

Edit: Read http://stackoverflow.com/questions/1083142/what-s-the-correct-way-to-use-printf-to-print-a-clock-t

[chbaker0]

Also, I hope you realize that this is still undefined behavior:

template <glm::precision P, template <typename, glm::precision> class vecType>
GLM_FUNC_QUALIFIER vecType<float, P> fastAbs(vecType<float, P> x)
{
    int* Pointer = reinterpret_cast<int*>(&x[0]);
    Pointer[0] &= 0x7fffffff;
    Pointer[1] &= 0x7fffffff;
    Pointer[2] &= 0x7fffffff;
    Pointer[3] &= 0x7fffffff;
    return x;
}

if you pass it a vec2 for example, Pointer[2] and Pointer[3] will index into non-existent memory locations, or worse, into other variable's memory. Also, it behaves totally incorrectly if passed a dvec*. And what if it's used on a platform where sizeof(int) != sizeof(float)? I don't understand what this code is supposed to accomplish anyway; it's called fastAbs but I find it really hard to believe this will be any faster than using std::abs on each element, or even just doing

if(x < 0.0)
    x = -x;

for each element x.