[PATCH 3/3] msvcp140_atomic_wait: Add __std_atomic_wait_direct implementation.

[Piotr Caban]

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52821
Signed-off-by: Piotr Caban <piotr(a)codeweavers.com>
---
  dlls/msvcp140_atomic_wait/main.c              |  7 ++
  .../msvcp140_atomic_wait.spec                 |  2 +-
  .../tests/msvcp140_atomic_wait.c              | 70 +++++++++++++++++++
  3 files changed, 78 insertions(+), 1 deletion(-)

[Marvin]

Hi,

While running your changed tests, 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:
https://testbot.winehq.org/JobDetails.pl?Key=113596

Your paranoid android.


=== w7u_2qxl (32 bit report) ===

Report validation errors:
msvcp140_atomic_wait:msvcp140_atomic_wait has no test summary line (early exit of the main process?)
msvcp140_atomic_wait:msvcp140_atomic_wait returned a non-zero exit code despite reporting no failures

=== w7u_adm (32 bit report) ===

Report validation errors:
msvcp140_atomic_wait:msvcp140_atomic_wait has no test summary line (early exit of the main process?)
msvcp140_atomic_wait:msvcp140_atomic_wait returned a non-zero exit code despite reporting no failures

=== w7u_el (32 bit report) ===

Report validation errors:
msvcp140_atomic_wait:msvcp140_atomic_wait has no test summary line (early exit of the main process?)
msvcp140_atomic_wait:msvcp140_atomic_wait returned a non-zero exit code despite reporting no failures