You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[New msys2-runtime version] Cygwin: uname: add host machine tag to sysname.
Cygwin: uname: add host machine tag to sysname.
If the Cygwin dll's architecture is different from the host system's
architecture, append an additional tag that indicates the host system
architecture (the Cygwin dll's architecture is already indicated in
machine).
Signed-off-by: Jeremy Drake <cygwin@jdrake.com>
(cherry picked from commit 7923059bff6c120c6fb74b63c7553ea345c0a8f3)
[New msys2-runtime version] Cygwin: cache IsWow64Process2 host arch in wincap.
Cygwin: cache IsWow64Process2 host arch in wincap.
This was already used in the FAST_CWD check, and could be used in a
couple other places.
I found the "emulated"/process value returned from the function largely
useless, so I did not cache it. It is useless because, as the docs say,
it is set to IMAGE_FILE_MACHINE_UNKNOWN (0) if the process is not
running under WOW64, but Microsoft also doesn't consider x64-on-ARM64 to
be WOW64, so it is set to 0 regardless if the process is ARM64 or x64.
You can tell the difference via
GetProcessInformation(ProcessMachineTypeInfo), but for the current
process even that's overkill: what we really want to know is the
IMAGE_FILE_MACHINE_* constant for the Cygwin dll itself, which is
conveniently located in memory already, so cache that in wincap also for
easy comparisons.
Signed-off-by: Jeremy Drake <cygwin@jdrake.com>
(cherry picked from commit 46f7bcc1e575826f6d3e4a5770ae61423d9be5a9)
[New msys2-runtime version] Cygwin: uname: add host machine tag to sysname.
msys2/msys2-runtime@8d847f4
[New msys2-runtime version] Cygwin: cache IsWow64Process2 host arch in wincap.
msys2/msys2-runtime@fe383b0
The text was updated successfully, but these errors were encountered: