fix: correct match offset truncation for buffers larger than 4GB#257
Open
p1geondove wants to merge 3 commits intodarvid:mainfrom
Open
fix: correct match offset truncation for buffers larger than 4GB#257p1geondove wants to merge 3 commits intodarvid:mainfrom
p1geondove wants to merge 3 commits intodarvid:mainfrom
Conversation
Co-authored-by: github-actions <david+hyperscan-ci@d10i.dev>
5ba9006 to
99cdf90
Compare
Author
|
shit i didnt have a gpg key, so i just made one, thought i had to cloes the request and make a new one, well its open again.. |
This file contains hidden or 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
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.
hyperscan does support long long to and from for stream and vector mode, just the indivudial chunks cant be longer than 2^32-1
i added basic tests for that, altho they are really slow, could oom and so on