revert recent regex-syntax interval set optimizations #1102
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
This reverts commit 6d2b09e. Sadly I just don't have the time to fix this code myself. It's too subtle. So I'm just reverting it entirely for now. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63155 Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63153 Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63168 Ref #1051
BurntSushi
force-pushed
the
ag/interval-panics
branch
from
310a0c8
to
8081a3d
Compare
Licheam
added a commit
to Licheam/regex
that referenced
this pull request
Oct 12, 2023
Fix the `push` function in rust-lang#1051
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.
Specifically, this PR: #1051
Multiple bugs were caught by OSS-fuzz. Ideally we'd just fix them, but this code is extremely subtle and we'll need to make these changes more carefully (if at all).
cc @Licheam if you want to take a crack at fixing these. I think we'll maybe want to land one optimization at a time perhaps? And I'll have to insist on better unit test coverage as well.