aboutsummaryrefslogtreecommitdiff
path: root/client/asmjit/core/virtmem.h
diff options
context:
space:
mode:
Diffstat (limited to 'client/asmjit/core/virtmem.h')
-rw-r--r--client/asmjit/core/virtmem.h145
1 files changed, 0 insertions, 145 deletions
diff --git a/client/asmjit/core/virtmem.h b/client/asmjit/core/virtmem.h
deleted file mode 100644
index 8d3ee01..0000000
--- a/client/asmjit/core/virtmem.h
+++ /dev/null
@@ -1,145 +0,0 @@
-// AsmJit - Machine code generation for C++
-//
-// * Official AsmJit Home Page: https://asmjit.com
-// * Official Github Repository: https://github.com/asmjit/asmjit
-//
-// Copyright (c) 2008-2020 The AsmJit Authors
-//
-// This software is provided 'as-is', without any express or implied
-// warranty. In no event will the authors be held liable for any damages
-// arising from the use of this software.
-//
-// Permission is granted to anyone to use this software for any purpose,
-// including commercial applications, and to alter it and redistribute it
-// freely, subject to the following restrictions:
-//
-// 1. The origin of this software must not be misrepresented; you must not
-// claim that you wrote the original software. If you use this software
-// in a product, an acknowledgment in the product documentation would be
-// appreciated but is not required.
-// 2. Altered source versions must be plainly marked as such, and must not be
-// misrepresented as being the original software.
-// 3. This notice may not be removed or altered from any source distribution.
-
-#ifndef ASMJIT_CORE_VIRTMEM_H_INCLUDED
-#define ASMJIT_CORE_VIRTMEM_H_INCLUDED
-
-#include "../core/api-config.h"
-#ifndef ASMJIT_NO_JIT
-
-#include "../core/globals.h"
-
-ASMJIT_BEGIN_NAMESPACE
-
-//! \addtogroup asmjit_virtual_memory
-//! \{
-
-// ============================================================================
-// [asmjit::VirtMem]
-// ============================================================================
-
-//! Virtual memory management.
-namespace VirtMem {
-
-//! Virtual memory and memory mapping flags.
-enum Flags : uint32_t {
- //! No access flags.
- kAccessNone = 0x00000000u,
- //! Memory is readable.
- kAccessRead = 0x00000001u,
- //! Memory is writable (implies read access).
- kAccessWrite = 0x00000002u,
- //! Memory is executable (implies read access).
- kAccessExecute = 0x00000004u,
-
- //! A combination of `kAccessRead | kAccessWrite`
- kAccessReadWrite = 0x00000003u,
-
- //! Use a `MAP_JIT` flag available on Apple platforms (OSX Mojave+), which
- //! allows JIT code to be executed in OSX bundles. This flag is not turned
- //! on by default, because when a process uses `fork()` the child process
- //! has no access to the pages mapped with `MAP_JIT`, which could break code
- //! that doesn't expect this behavior.
- kMMapEnableMapJit = 0x00000010u,
-
- //! Not an access flag, only used by `allocDualMapping()` to override the
- //! default allocation strategy to always use a 'tmp' directory instead of
- //! "/dev/shm" (on POSIX platforms). Please note that this flag will be
- //! ignored if the operating system allows to allocate an executable memory
- //! by a different API than `open()` or `shm_open()`. For example on Linux
- //! `memfd_create()` is preferred and on BSDs `shm_open(SHM_ANON, ...)` is
- //! used if SHM_ANON is defined.
- kMappingPreferTmp = 0x80000000u
-};
-
-//! Virtual memory information.
-struct Info {
- //! Virtual memory page size.
- uint32_t pageSize;
- //! Virtual memory page granularity.
- uint32_t pageGranularity;
-};
-
-//! Dual memory mapping used to map an anonymous memory into two memory regions
-//! where one region is read-only, but executable, and the second region is
-//! read+write, but not executable. Please see \ref VirtMem::allocDualMapping()
-//! for more details.
-struct DualMapping {
- //! Pointer to data with 'Read' or 'Read+Execute' access.
- void* ro;
- //! Pointer to data with 'Read-Write' access, but never 'Write+Execute'.
- void* rw;
-};
-
-//! Returns virtual memory information, see `VirtMem::Info` for more details.
-ASMJIT_API Info info() noexcept;
-
-//! Allocates virtual memory by either using `VirtualAlloc()` (Windows)
-//! or `mmap()` (POSIX).
-//!
-//! \note `size` should be aligned to a page size, use \ref VirtMem::info()
-//! to obtain it. Invalid size will not be corrected by the implementation
-//! and the allocation would not succeed in such case.
-ASMJIT_API Error alloc(void** p, size_t size, uint32_t flags) noexcept;
-
-//! Releases virtual memory previously allocated by \ref VirtMem::alloc() or
-//! \ref VirtMem::allocDualMapping().
-//!
-//! \note The size must be the same as used by \ref VirtMem::alloc(). If the
-//! size is not the same value the call will fail on any POSIX system, but
-//! pass on Windows, because of the difference of the implementation.
-ASMJIT_API Error release(void* p, size_t size) noexcept;
-
-//! A cross-platform wrapper around `mprotect()` (POSIX) and `VirtualProtect`
-//! (Windows).
-ASMJIT_API Error protect(void* p, size_t size, uint32_t flags) noexcept;
-
-//! Allocates virtual memory and creates two views of it where the first view
-//! has no write access. This is an addition to the API that should be used
-//! in cases in which the operating system either enforces W^X security policy
-//! or the application wants to use this policy by default to improve security
-//! and prevent an accidental (or purposed) self-modifying code.
-//!
-//! The memory returned in the `dm` are two independent mappings of the same
-//! shared memory region. You must use \ref VirtMem::releaseDualMapping() to
-//! release it when it's no longer needed. Never use `VirtMem::release()` to
-//! release the memory returned by `allocDualMapping()` as that would fail on
-//! Windows.
-//!
-//! \remarks Both pointers in `dm` would be set to `nullptr` if the function fails.
-ASMJIT_API Error allocDualMapping(DualMapping* dm, size_t size, uint32_t flags) noexcept;
-
-//! Releases the virtual memory mapping previously allocated by
-//! \ref VirtMem::allocDualMapping().
-//!
-//! \remarks Both pointers in `dm` would be set to `nullptr` if the function succeeds.
-ASMJIT_API Error releaseDualMapping(DualMapping* dm, size_t size) noexcept;
-
-} // VirtMem
-
-//! \}
-
-ASMJIT_END_NAMESPACE
-
-#endif
-#endif // ASMJIT_CORE_VIRTMEM_H_INCLUDED