Update pcre2 to v10.44 #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r heap frame information
When using -t or its variants the timing results with a modern CPU where not very significant even with 4 decimal digits. While at it, move the factor calculation that can be done with integer arithmetic and even optimized out for the more common case when CLOCKS_PER_SEC == 1000000 out of the denominator.
Recent code uses C99 syntax (as reported in #163, and therefore it will fail to build unless C99 (or higher) support is required by the compiler (gcc >= 5 does it by default). For those unfortunate to need an older compiler that does require a flag to enable that, make sure that both autoconf and cmake make it explicit. While testing the change with the ancient autoconf version listed as a prerequisite, noticed that the LT_INIT syntax introduced with 91485e5 (Update configure.ac for latest version of autoconf., 2021-02-02), was not supported, so update the autoconf minimum as well.
It doesn't change much in practice, but helps clarify the interfaces of some functions that were either documented with the wrong type or had mismatching types between declaration and implementation.
Reverting several reserved characters that were removed from the previous release, and that are only referencing as "@missing@ in DerivedBidiClass.txt
* ucptest: regenerate testoutput Last sync with 1a5fcd (Remove unused variables in ucptest.c and update test data for added properties, 2022-04-25), and showing significant differences. * fix `findprop +` with UTF-8 characters and duplicated other case
Starting with Unicode 15, the provided DerivedBidiClass data file reports different default values to use for unassigned characters in different groups. Process the additional hints for that specific file, and allow overriding the values later if more specific. Since that was previously forbidden, change get_other_case() to report when no valid value could be provided and allow skipping conflicting rule lines that required that restriction. While at it, Allow using the long identifiers in `ucptest` with the `find bidi` command (underscores also allowed).
Compilers had become far more creative about optimizing code that might be considered undefined behaviour, so improve our integer overflow checking to prevent any possible miscompilations. While at it, expand the use of the checks to pcre2test to fix a similar problem to the one that was tackled in pcre2_compile. Prefer (if available) a builtin provided by the compiler.
…(#202) `ucptest` was misbehaving and showing the wrong properties and finding the wrong characters.
…tions --case-restrict and --no-ucp.
…(for an error message) before any potential use.
I'm going to commit this because it looks sensible, though I know nothing about MSVC and only a bit about CMake. Note that the failing actions on this PR are unrelated.
The test is now done in sljitConfigCPU.h
…ight of further issues
…uences like "){9){123}", causing a JIT timeout.
This is the only breaking change since the previous update https://ziglang.org/documentation/0.12.0/std/#std.Build.Step.Compile.installHeader Co-authored-by: Jordan Griege <>
…e tested with JIT, to avoid oss-fuzz timeouts.
Since a8a875e (windows: integrate visibility attributes without conflicts (#249), 2023-05-16), PCRE2_EXPORT was meant to be defined as an empty value for compilers that don't support -fvisibility in *NIX, but a branch was left uncovered by mistake resulting in compilation issues with propietary compilers in at least Solaris and AIX. define PCRE2_EXPORT even if the compiler is not GCC compatible.
remove files that are not in the upstream repo update chartables update config files
'for' loop initial declarations are only allowed in C99 mode
|
Really done now, thanks again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.