| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| fix-privacy-breach.patch | no | |||||
| set-doc-dir.diff | no | |||||
| disable-valgrind_unittest.diff | no | |||||
| no-jsoncheckertest.diff | remove the unittest using bin/jsonchecker/* as that one is removed from the tarball due to having this insane 'good not evil' "license |
Rene Engelhard <rene@debian.org> | no | debian | ||
| gcc7.diff | fix build with gcc7 From https://github.com/miloyip/rapidjson/commit/fe19b7b6016d446722621fb407738209d1a911e8 and https://github.com/miloyip/rapidjson/commit/cba45fe9de6923b858edb0780e257b7257aa4f7b |
no | debian | |||
| 0001-Fix-Wclass-memaccess-warnings-errors.patch | [PATCH 1/3] Fix -Wclass-memaccess warnings/errors Recent GCC versions warn about using memcpy/memmove to write to a class pointer (-Wclass-memaccess). Avoid the warnings by casting to void* first. Closes #1086. Closes #1205. Closes #1246. |
Philipp A Hartmann <pah@qo.cx> | no | 2018-07-15 | ||
| 0002-Fix-Wsign-conversion-warnings-errors.patch | [PATCH 2/3] Fix -Wsign-conversion warnings/errors GCC 8 (incorrectly) warns about sign conversions in (constant) array size expressions: change the sign of the result [-Werror=sign-conversion] char schemaBuffer_[128 * 1024]; Make these expressions unsigned by adding a 'u' suffix to the first operands. |
Philipp A Hartmann <pah@qo.cx> | no | 2018-07-15 | ||
| 0003-Suppress-Wformat-overflow-warning-error.patch | [PATCH 3/3] Suppress -Wformat-overflow warning/error GCC 7 and later warn about overflow/truncation when using sprintf and related functions with fixed-size buffers. Suppress the warning in schematest.cpp. |
Philipp A Hartmann <pah@qo.cx> | no | 2018-07-15 | ||
| python3.diff | =================================================================== | no | ||||
| 0001-support-IBM-PowerPC-ppc64-ppc64le-and-XL-compiler.patch | [PATCH] support IBM PowerPC / ppc64 / ppc64le and XL compiler Avoid POWER platform compiling error and support IBM XL C++ compiler on Linux / AIX. |
Wu Zhao <wuzhaozju@gmail.com> | no | 2016-10-26 | ||
| 0001-CMake-do-not-pass-march-native-or-mcpu-native-when-c.patch | [PATCH] CMake: do not pass -march=native or -mcpu=native when crosscompiling | Rolf Eike Beer <eb@emlix.com> | no | 2017-11-24 | ||
| deal-with-Werror-type-limits.patch | no | |||||
| gcc12_encdedstreamtest.patch | [PATCH] encdedstreamtest: fix use-after-free compile error with gcc-12 | Tom Briden <tom@decompile.me.uk> | no | 2022-05-15 | ||
| gcc12_valuetest.patch | [PATCH] valuetest: fix potential write of terminating nul past the end of the destination Fixes 2 compile errors with gcc-12, eg: tesunittest/valuetest.cpp:1516:30: error: 'sprintf' may write a terminating nul past the end of the destination [-Werror=format-overflow=] test/unittest/valuetest.cpp:1516:20: note: 'sprintf' output between 2 and 11 bytes into a destination of size 10 |
Tom Briden <tom@decompile.me.uk> | no | 2022-05-15 | ||
| 0001-Removed-non-compiling-assignment-operator.-Fixed-718.patch | [PATCH 1/2] Removed non-compiling assignment operator. Fixed #718 | Janusz Chorko <janusz.chorko@apdu.pl> | no | 2016-08-26 | ||
| 0002-Explicitly-disable-copy-assignment-operator.patch | [PATCH 2/2] Explicitly disable copy assignment operator | Janusz Chorko <janusz.chorko@apdu.pl> | no | 2016-08-26 | ||
| 0001-Avoid-inheritance-from-std-iterator.patch | [PATCH] Avoid inheritance from std::iterator Instead of inheriting from the deprecated std::iterator template, define the member typedefs needed for std::iterator_traits directly. Closes #1131. |
"Philipp A. Hartmann" <pah@qo.cx> | no | 2017-12-12 | ||
| 0001-Avoid-warnings-when-using-std-c-20-and-clang-10-use-.patch | [PATCH] Avoid warnings when using -std=c++20 and clang 10: use three way comparision for iterators when possible. (#1667) /data/mwrep/res/osp/RapidJson/20-0-0-0/include/rapidjson/document.h:729:58: error: use of overloaded operator '!=' is ambiguous (with operand types 'rapidjson::GenericValue<rapidjson::UTF8<char>, rapidjson::MemoryPoolAllocator<rapidjson::CrtAllocator> >::MemberIterator' (aka 'rapidjson::GenericMemberIterator<false, rapidjson::UTF8<char>, rapidjson::MemoryPoolAllocator<rapidjson::CrtAllocator> >') and 'rapidjson::GenericValue<rapidjson::UTF8<char>, rapidjson::MemoryPoolAllocator<rapidjson::CrtAllocator> >::MemberIterator') for (MemberIterator m = MemberBegin(); m != MemberEnd(); ++m) |
"Romain Geissler @ Amadeus" <romain.geissler@amadeus.com> | no | 2020-03-20 | ||
| 0001-Three-way-comparison-for-CLang-10-fix-1679.patch | [PATCH] Three-way comparison for CLang 10 fix (#1679) C++20 features must enable additional functionality, not to change interface completely |
Nikolay <211292+kolya7k@users.noreply.github.com> | no | 2020-03-30 | ||
| 0001-Fix-recursive-operator-call-in-C-20-1846.patch | [PATCH] Fix recursive operator== call in C++20 (#1846) | Laurent Stacul <laurent.stacul@amadeus.com> | no | 2021-02-22 | ||
| 0001-gate-definition-of-symmetric-equality-operators-on-i.patch | [PATCH] gate definition of symmetric equality operators on impl, not lib These operators call themselves recursively if C++20 semantics are present in the compiler, regardless of standard library support for the operator; therefore the test should be on __cpp_impl_three_way_comparison, not __cpp_lib_[...]. This fixes the Value.EqualtoOperator test when the language standard is set to C++20 and the standard library does not yet define the library support macro. |
Kent Ross <k@mad.cash> | no | 2022-03-14 | ||
| 0001-do-not-define-operator-in-C-20.patch | [PATCH] do not define operator!= in C++20 A change to the semantics of equality operator rewriting in C++20 (P2468R2: The Equality Operator You Are Looking For) means that operator== may not be rewritten with reversed operands if operator!= is also defined. Since operator!= can normally be synthesized from operator== regardless in this language standard, we can and should avoid defining those when the new language semantics are available. This fixes the compilation of tests (and probably consuming code) in C++20 onwards for compilers that implement this new semantic, including recent nightly builds of clang-16. |
Kent Ross <k@mad.cash> | no | 2022-11-03 |