There are only three unused format flags left. I will soon submit changes
which add four more format flags.
I've noticed that format flags generally fall into two groups:
* The first group consists of flags describing the content of a pixel
format, e.g. whether or not this is a depth format, or whether this is
a blocked format. These flags are the same for all resource types.
* The second group consists of flags describing capabilities of the
implementation with this format. These can and do vary by resource
type.
Only the second group needs to be stored per-resource-type.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/79
On Tue May 17 08:19:21 2022 +0000, Huw Davies wrote:
> Actually, we don't de-populate the list on interface removals, so this
> should be ok. I'll take another look.
> (and figure out if there's an equivalent we could do on macOS)
System event sockets (`PF_SYSTEM`, `SYSPROTO_EVENT`) are what you want here. They have the ability to notify the caller when an interface appears (`KEV_DL_IF_ATTACHED`), when it is about to disappear (`KEV_DL_IF_DETACHING`), and when it has vanished (`KEV_DL_IF_DETACHED`).
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/78#note_966
On both Mac and Linux under Wow64, after ~120 threads are created, the 64-bit stacks start to be allocated above 4GB.
This triggered crashes in alloc_fs_sel() and when the result of get_cpu_area() was used.
(On Mac the ntdll threadpool tests reproduced this, but on both platforms a test app that created 256 threads also worked).
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/85