Have you tried it on another computer? It appears to me that x,y,z,w are being optimized by doing the math in CPU registers. When declaring them at the top instead of right before they are used, you are causing blitzMax to store the variables in memory instead. Also Print, DebugLog, etc... would also necessitate putting the values into memory.
I remember some old pentiums having bugs in the math coprocessor, possibly the same thing happening here?
I remember some old pentiums having bugs in the math coprocessor, possibly the same thing happening here?