Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://winetestbot.dolphin/JobDetails.pl?Key=105
Your paranoid android.
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://winetestbot.dolphin/JobDetails.pl?Key=86
Your paranoid android.
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://winetestbot.dolphin/JobDetails.pl?Key=43
Your paranoid android.
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=19631
Your paranoid android
Vincent Povirk wrote:
> > + case VT_I8:
> > + case VT_UI8:
> > + case VT_R8:
> > + return v1->u.uhVal.QuadPart - v2->u.uhVal.QuadPart;
>
> Won't this only compare the low part on x86?
In reality the only possible variant type supposed to be seen by this
helper is VT_UI2, everyth
> + case VT_I8:
> + case VT_UI8:
> + case VT_R8:
> + return v1->u.uhVal.QuadPart - v2->u.uhVal.QuadPart;
Won't this only compare the low part on x86?
