These should be stored in function's children vector.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

mingw-w64 defines __forceinline (and therefore FORCEINLINE) as
"extern __inline__ __attribute__((__always_inline__,__gnu_inline__)). This means
that COM inline wrappers specify multiple storage classes and hence cannot be
compiled.

Wine defines FORCEINLINE simply as "inline" (and uses "static" everywhere), so
this is a non-issue for Wine. However, since Wine and mingw-w64 share the source
code of widl and of most IDL headers, this patch changes the definition for both
projects.

There's no reason to force inlining here, especially since the wrappers need to
be manually enabled, and we don't need to match PSDK semantics where these
wrappers don't even exist.

In practice, use "__inline__" instead of "inline" for GNU C targets, to preserve
compatibility with C89 in mingw-w64 headers.

Add relevant structures to include/mscvpdb.h.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Introduce relevant structures in include/wine/msvcpdb.h.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

GCC12.2 emits a warning here.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

This usually doesn't go through the normal presentation paths.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52954

This reverts commit 27f417eb.
It breaks the tests.

This reverts commit 28e0d8ff.
It breaks the tests.

Change strategy for resetting local scope when unloading a module.
Old strategy was keeping the local scoped symbol alive on some code path when
unloading a module.
This caused some bad behavior as we kept a pointer to a deleted object.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

This happens because the llvmpipe virtual GPU is not in the RandR provider list
when there is a hardware GPU driving the screen. So LUID for the llvmpipe is
not generated in such cases.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52931Signed-off-by: Zhiyi Zhang <zzhang@codeweavers.com>

Some Wine tests are multi-threaded or start child processes which can
result in traces and failure messages being garbled which prevents them
from being recognized by continuous integration tools.
So printing the test messages is now serialized. Note that if a process
crashes while holding the mutex, that mutex will be abandoned and not
cause a deadlock.

MSDN states, a NULL InfoValue parameter will return as the length.
unixODBC which we currently use, handles this scenario.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53714Signed-off-by: Alistair Leslie-Hughes <leslie_alistair@hotmail.com>