VCMP and VCMPE were the other way around

- This was due to a misunderstanding of what the E in VCMPE means.
- The E refers to an exception being raised when a QNaN is encountered.
- Added unit tests for VCMP{E}

src/backend_x64/jitstate.cpp

@@ -120,7 +120,7 @@ void JitState::SetFpscr(u32 FPSCR) {
     if (Common::Bit<24>(FPSCR)) {
         // VFP Flush to Zero
         //guest_MXCSR |= (1 << 15); // SSE Flush to Zero
-        guest_MXCSR |= (1 << 6);  // SSE Denormals are Zero
+        //guest_MXCSR |= (1 << 6);  // SSE Denormals are Zero
     }
 }