Explicit calling convention for d-linked function
When compiled with `target_cpu = "x86"` several VirtualAddressSpaceTest's crashed with segmentation fault when calling VirtualAlloc2. Explicitly specifying calling convention fixed the issue. Change-Id: Ie505006be0d44525c935c89b84caa2c373cea566 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3501836 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Dmitrii Tsykunov <dtsykunov1@yandex-team.ru> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#79436}
This commit is contained in:
parent
87f806717c
commit
e897511155
@ -722,15 +722,16 @@ void OS::Initialize(bool hard_abort, const char* const gc_fake_mmap) {
|
||||
g_hard_abort = hard_abort;
|
||||
}
|
||||
|
||||
typedef PVOID (*VirtualAlloc2_t)(HANDLE, PVOID, SIZE_T, ULONG, ULONG,
|
||||
MEM_EXTENDED_PARAMETER*, ULONG);
|
||||
typedef PVOID(__stdcall* VirtualAlloc2_t)(HANDLE, PVOID, SIZE_T, ULONG, ULONG,
|
||||
MEM_EXTENDED_PARAMETER*, ULONG);
|
||||
VirtualAlloc2_t VirtualAlloc2 = nullptr;
|
||||
|
||||
typedef PVOID (*MapViewOfFile3_t)(HANDLE, HANDLE, PVOID, ULONG64, SIZE_T, ULONG,
|
||||
ULONG, MEM_EXTENDED_PARAMETER*, ULONG);
|
||||
typedef PVOID(__stdcall* MapViewOfFile3_t)(HANDLE, HANDLE, PVOID, ULONG64,
|
||||
SIZE_T, ULONG, ULONG,
|
||||
MEM_EXTENDED_PARAMETER*, ULONG);
|
||||
MapViewOfFile3_t MapViewOfFile3 = nullptr;
|
||||
|
||||
typedef PVOID (*UnmapViewOfFile2_t)(HANDLE, PVOID, ULONG);
|
||||
typedef PVOID(__stdcall* UnmapViewOfFile2_t)(HANDLE, PVOID, ULONG);
|
||||
UnmapViewOfFile2_t UnmapViewOfFile2 = nullptr;
|
||||
|
||||
void OS::EnsureWin32MemoryAPILoaded() {
|
||||
|
Loading…
Reference in New Issue
Block a user