pcre2: Update to upstream version 10.42 (take two) - #70472
Conversation
Changelog: https://github.com/PCRE2Project/pcre2/blob/pcre2-10.42/ChangeLog This fixes support for RISC-V architectures in the sljit library, so we enable the module's compilation for `rv64` too.
|
Added a I don't know if there are other implications for that upstream change which caused this error spam in the first place. |
|
While the pcre2 docs don't appear to specify anything about the required behavior of the passed free function, the standard C free function is explicitly specified to do nothing when passed a null pointer, so I would assume this is just caused by some simplifications and them removing some otherwise unnecessary null checks. |
|
Cherry-picked for 3.6. |
| #if MAC_OS_X_VERSION_MIN_REQUIRED >= 110000 | ||
| pthread_jit_write_protect_np(enable_exec); | ||
| #elif defined(__clang__) | ||
| if (__builtin_available(macOS 11.0, *)) | ||
| pthread_jit_write_protect_np(enable_exec); | ||
| #else | ||
| #error "Must target Big Sur or newer" |
There was a problem hiding this comment.
As of this PR cherry-picked into the 3.x branch, I am unable to compile Godot on macOS, because Godot 3.x targets macOS 10.15+, and this change breaks support for macOS < 11.0.
If I revert this PR, it compiles fine (fails on linking but that's a different problem).
There was a problem hiding this comment.
I am unable to compile Godot on macOS, because Godot 3.x targets macOS 10.15+, and this change breaks support for macOS < 11.0.
Target version should be changed to 11.0, 10.15 for arm64 existed only as the early alphas.
pcre2: Update to upstream version 10.42 (take two)
pcre2: Update to upstream version 10.42 (take two)
Changelog: https://github.com/PCRE2Project/pcre2/blob/pcre2-10.42/ChangeLog
This fixes support for RISC-V architectures in the sljit library, so we enable the module's compilation for
rv64too.Redo of #70447 which I reverted due to a regression described there:
#70447 (comment)
Fixes #76174
From @vonagam:
My early findings:
Backtrace:
It probably comes from this change:
We likely need to change our
_regex_free(and maybe_regex_malloc) to take this new heap vector into account somehow.