Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
home:Ledest:erlang
erlang
0592-remove-typo-fixes-to-vendored-code.patch
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File 0592-remove-typo-fixes-to-vendored-code.patch of Package erlang
From fd44ec9d0c0fa63f867825e04a3846219afeb0ef Mon Sep 17 00:00:00 2001 From: Paul Ivanov <pi@berkeley.edu> Date: Sat, 2 Dec 2023 23:23:41 -0800 Subject: [PATCH 2/2] remove typo fixes to vendored code --- erts/emulator/asmjit/core.h | 2 +- erts/emulator/asmjit/core/api-config.h | 2 +- erts/emulator/asmjit/core/jitallocator.h | 2 +- erts/emulator/asmjit/core/virtmem.h | 2 +- erts/emulator/asmjit/x86/x86opcode_p.h | 6 +++--- erts/emulator/zlib/inftrees.h | 2 +- erts/emulator/zlib/zlib.h | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/erts/emulator/asmjit/core.h b/erts/emulator/asmjit/core.h index 878c5ffa66..e586734e49 100644 --- a/erts/emulator/asmjit/core.h +++ b/erts/emulator/asmjit/core.h @@ -757,7 +757,7 @@ namespace asmjit { //! //! There is no function that would return the number of unbound labels as this is completely unimportant from //! CodeHolder's perspective. If a label is not used then it doesn't matter whether it's bound or not, only actually -//! used labels matter. After a Label is bound it's possible to query its offset relative to the start of the +//! used labels matter. After a Label is bound it's possible to query its offset offset relative to the start of the //! section where it was bound: //! //! ``` diff --git a/erts/emulator/asmjit/core/api-config.h b/erts/emulator/asmjit/core/api-config.h index b12832f863..60c9d5244e 100644 --- a/erts/emulator/asmjit/core/api-config.h +++ b/erts/emulator/asmjit/core/api-config.h @@ -21,7 +21,7 @@ //! //! It's used to make sure that when user links to an incompatible version of AsmJit, it won't link. It has also some //! additional properties as well. When `ASMJIT_ABI_NAMESPACE` is defined by the user it would override the AsmJit -//! default, which makes it possible to use multiple AsmJit libraries within a single project, totally controlled +//! default, which makes it possible to use use multiple AsmJit libraries within a single project, totally controlled //! by the users. This is useful especially in cases in which some of such library comes from a third party. #ifndef ASMJIT_ABI_NAMESPACE #define ASMJIT_ABI_NAMESPACE _abi_1_9 diff --git a/erts/emulator/asmjit/core/jitallocator.h b/erts/emulator/asmjit/core/jitallocator.h index 1edc436df7..40af92924c 100644 --- a/erts/emulator/asmjit/core/jitallocator.h +++ b/erts/emulator/asmjit/core/jitallocator.h @@ -231,7 +231,7 @@ public: inline size_t usedSize() const noexcept { return _usedSize; } //! Returns the number of bytes unused by the allocator at the moment. inline size_t unusedSize() const noexcept { return _reservedSize - _usedSize; } - //! Returns the total number of bytes reserved by the allocator (sum of sizes of all blocks). + //! Returns the total number of bytes bytes reserved by the allocator (sum of sizes of all blocks). inline size_t reservedSize() const noexcept { return _reservedSize; } //! Returns the number of bytes the allocator needs to manage the allocated memory. inline size_t overheadSize() const noexcept { return _overheadSize; } diff --git a/erts/emulator/asmjit/core/virtmem.h b/erts/emulator/asmjit/core/virtmem.h index 2f7e86d5af..a5633a2081 100644 --- a/erts/emulator/asmjit/core/virtmem.h +++ b/erts/emulator/asmjit/core/virtmem.h @@ -194,7 +194,7 @@ enum class ProtectJitAccess : uint32_t { //! Protects access of memory mapped with MAP_JIT flag for the current thread. //! -//! \note This feature is only available on Apple hardware (AArch64) at the moment and uses a non-portable +//! \note This feature is only available on Apple hardware (AArch64) at the moment and and uses a non-portable //! `pthread_jit_write_protect_np()` call when available. //! //! This function must be called before and after a memory mapped with MAP_JIT flag is modified. Example: diff --git a/erts/emulator/asmjit/x86/x86opcode_p.h b/erts/emulator/asmjit/x86/x86opcode_p.h index 83b2f3e428..94a76f0481 100644 --- a/erts/emulator/asmjit/x86/x86opcode_p.h +++ b/erts/emulator/asmjit/x86/x86opcode_p.h @@ -45,7 +45,7 @@ struct Opcode { //! `pp` in instruction manuals. //! //! - `LL` field is used exclusively by AVX+ and AVX512+ instruction sets. It describes vector size, which is `L.128` - //! for XMM register, `L.256` for YMM register, and `L.512` for ZMM register. The `LL` field is omitted in case + //! for XMM register, `L.256` for for YMM register, and `L.512` for ZMM register. The `LL` field is omitted in case //! that instruction supports multiple vector lengths, however, if the instruction requires specific `L` value it //! must be specified as a part of the opcode. //! @@ -244,7 +244,7 @@ struct Opcode { // REX|VEX|EVEX B|X|R|W Bits // ------------------------- // - // NOTE: REX.[B|X|R] are never stored within the opcode itself, they are reserved by AsmJit are added + // NOTE: REX.[B|X|R] are never stored within the opcode itself, they are reserved by AsmJit are are added // dynamically to the opcode to represent [REX|VEX|EVEX].[B|X|R] bits. REX.W can be stored in DB as it's sometimes // part of the opcode itself. @@ -280,7 +280,7 @@ struct Opcode { // `L` or `LL` field in AVX/XOP/AVX-512 // ------------------------------------ // - // VEX/XOP prefix can only use the first bit `L.128` or `L.256`. EVEX prefix makes it possible to use also + // VEX/XOP prefix can only use the first bit `L.128` or `L.256`. EVEX prefix prefix makes it possible to use also // `L.512`. If the instruction set manual describes an instruction by `LIG` it means that the `L` field is ignored // and AsmJit defaults to `0` in such case. kLL_Shift = 29, diff --git a/erts/emulator/zlib/inftrees.h b/erts/emulator/zlib/inftrees.h index 1b6bfc3dd4..f53665311c 100644 --- a/erts/emulator/zlib/inftrees.h +++ b/erts/emulator/zlib/inftrees.h @@ -41,7 +41,7 @@ typedef struct { examples/enough.c found in the zlib distribtution. The arguments to that program are the number of symbols, the initial root table size, and the maximum bit length of a code. "enough 286 9 15" for literal/length codes - returns 852, and "enough 30 6 15" for distance codes returns 592. + returns returns 852, and "enough 30 6 15" for distance codes returns 592. The initial root table size (9 or 6) is found in the fifth argument of the inflate_table() calls in inflate.c and infback.c. If the root table size is changed, then these maximum sizes would be need to be recalculated and diff --git a/erts/emulator/zlib/zlib.h b/erts/emulator/zlib/zlib.h index 8fe4dbb813..953cb5012d 100644 --- a/erts/emulator/zlib/zlib.h +++ b/erts/emulator/zlib/zlib.h @@ -729,7 +729,7 @@ ZEXTERN int ZEXPORT deflateParams OF((z_streamp strm, Then no more input data should be provided before the deflateParams() call. If this is done, the old level and strategy will be applied to the data compressed before deflateParams(), and the new level and strategy will be - applied to the data compressed after deflateParams(). + applied to the the data compressed after deflateParams(). deflateParams returns Z_OK on success, Z_STREAM_ERROR if the source stream state was inconsistent or if a parameter was invalid, or Z_BUF_ERROR if -- 2.35.3
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor
